Recipes for agents

Recipes are step-by-step instructions, with literal calls, that the MCP server gives assistants through the docs tool, each at docs://recipes/<slug>. They are the same ones published here: one source. They are in English because models follow them best that way; the assistant answers you in your language.

Each step of a recipe is a manage_resource call on a resource (cases, sends, evidence…), the same one the assistant would see with list_resources. See How the assistant works.

An assistant asks for them like this:

docs({})                                                     // the index
docs({ q: "notify the demandado" })                          // search
docs({ uri: "docs://recipes/send-an-article-8-notification" }) // read one

Notify

• Send an art. 8 (Ley 2213) notification: prepare the personal notification and request its send; you confirm.
• Send a correo con constancia de entrega: an email with no case (a formal demand, a collection letter, a contract notice), with the same evidence; the agent prepares the draft and you add the sworn recipients and send it in the panel.
• Send outside court hours: read the two dates of a send and propose when it leaves; you decide.
• Confirm pending sends: which requests wait for your confirmation, when they expire, and the link to confirm in the panel.
• Import a CSV batch: cases and drafts from one file; the failed rows come back as a CSV to fix.
• Send a batch: check that an import's drafts are ready and follow the batch send, which you make in the panel with one sworn statement per row.
• Manage message templates: create and correct the firm's templates; the art. 8 statements are never touched.
• Manage the address book: saved addresses per party, with where each came from; the sworn statement is still yours on each send.

Cases

• Find a case by radicado: from the 23-digit number to the case.
• Correct a case: a wrong radicado, juzgado or party. They are edited while no notification has left draft; what was sent is evidence and is never edited.
• Track deadlines: the terms per recipient in business days, an estimate: the judge decides.

Delivery and evidence

• Check a notification status: what happened with each recipient.
• What counts as delivered: delivery versus indicio, in the right words. A message having been opened is an indicio, not proof it was read.
• Handle a bounce: who was not notified at that address and what you can do; a new address is added by you, under oath.
• Download evidence for a perito: the signed constancia and the .zip package, with their hashes.
• Verify a constancia: by code or by the PDF's hash.
• Draft a memorial: the draft for the juzgado with the constancia; you review, sign and file it.
• Report a court outcome: accepted, rejected or nulidad; it is not evidence.

Account and integrations

• Top up credits: an agent does not buy: it tells you where to.
• Download an invoice: the electronic invoice as PDF or the XML DIAN validated; the download is recorded.
• Set up a webhook: have your own system receive, signed, each send, delivery, bounce, acuse and constancia.

Affiliates

The affiliate server (/mcp/afiliados) hands out its own recipes, at docs://affiliate/<slug>, to affiliate tokens only. A firm token does not see them, and an affiliate token does not see the ones above.

• docs://affiliate/read-my-affiliate-dashboard: what was earned, what is pending, when it is paid, and the referral link.
• docs://affiliate/file-a-statement-invoice: upload a statement's electronic invoice and request its submission; you confirm it on /afiliados.
• docs://affiliate/check-my-kyc-status: whether the verification was reviewed, or why a payout has not arrived.

See MCP for affiliates.