Skip to main content
Glama

order_operation

Read-only

Order an operation: validates the input against the schema and returns the filled document package (Markdown; optionally DOCX/PDF base64 and structured JSON) with a checklist where every legal statement carries a mark (K checked / J reading / KM not verified) and a source URL. Each order gets a unique order_id. Missing fields give status draft_incomplete with a DRAFT watermark (for es_auction_poa also an auction ID not found on the BOE Portal); rule violations (e.g. more than 3 shareholders, UG with 50% payment) give validation_failed. Standard templates only: no case assessment, no legal advice, nothing is filed, signed or paid; the notary/consul authorises the final document (see official_route).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation_id": "<operation_id>",
      "input": "<input>"
    },
    "name": "order_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesInput per the operation's input_schema (list_operations {operation_id}).
formatsNoDefault [markdown, json]. docx/pdf add base64 files per document.
operation_idYesId of the operation to order, e.g. es_auction_poa (see list_operations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / operation_id / description
      Added value: +"Id of the operation to order, e.g. es_auction_poa (see list_operations)."
  2. Changed1 schema field changed
    • changedInput schema / properties / operation_id / enum
      Previous value: -[
      -  "es_auction_poa",
      -  "de_gmbh_formation"
      -]New value: +[
      +  "es_auction_poa",
      +  "de_gmbh_formation",
      +  "apostille_translation",
      +  "it_srls_formation",
      +  "fr_eurl_formation"
      +]
  3. Added

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing concrete outcome states: status draft_incomplete with a DRAFT watermark on missing fields (plus the es_auction_poa auction-ID-not-found case), and validation_failed on rule violations such as >3 shareholders or UG with 50% payment. The 'nothing is filed, signed or paid; the notary/consul authorises the final document' line is consistent with readOnlyHint=true and clarifies the safety boundary an agent would otherwise have to guess.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what is produced, then statuses, then scope disclaimers — a logical order with no filler sentences. It is dense with nested parentheses, which costs a little readability but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden and does so: output formats, checklist/marks semantics, order_id, and the two failure statuses are all covered. For a nested-input, enum-driven generator, an agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that 'input' is validated against the selected operation's own input_schema (retrievable via list_operations) and that format selection changes the returned payload (base64 DOCX/PDF per document). It does not elaborate further on the operation_id enum values beyond naming es_auction_poa as an example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource (order an operation) and describes the concrete artifact produced: a filled document package with a per-statement checklist, marks (K/J/KM) and source URLs. It partially differentiates from siblings by pointing at list_operations for the input schema and at official_route for the final authorisation, but never explicitly contrasts itself with fill_template or quote_action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: input must conform to the operation's input_schema obtainable via list_operations, and scope is limited to 'standard templates only: no case assessment, no legal advice, nothing is filed, signed or paid'. It lacks an explicit 'use X instead when...' routing statement against the adjacent fill_template/quote_action tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.