Skip to main content
Glama

list_operations

Read-only

List Mandate operations: ready document packages an agent can order: es_auction_poa (Spanish power of attorney to bid on the BOE Portal de Subastas), de_gmbh_formation (German GmbH/UG Musterprotokoll package), it_srls_formation (Italian SRL semplificata on the official video model), fr_eurl_formation (French single-member SARL on the statutory model articles) and apostille_translation (EU27: apostille or exemption, competent authority, e-Apostille, sworn translation). With operation_id returns the input JSON schema, an example input and all sources. Free during beta.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO country code (ES, DE, IT, FR) or EU for the cross-border apostille_translation.
operation_idNoOptional: return one operation with input_schema and example_input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Optional ISO country code (ES, DE)."New value: +"Optional ISO country code (ES, DE, IT, FR) or EU for the cross-border apostille_translation."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the expanded return payload when operation_id is supplied (input JSON schema, example input, all sources) and the 'free during beta' pricing caveat — both useful for an agent deciding whether to call and what it will get back.

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-loaded with the core action and the catalog enumeration, and the operation_id behavior plus beta note are placed after. The parenthetical operation list is dense but it is factual content rather than filler, so it earns its space despite the length.

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?

For a two-optional-parameter, read-only catalog tool with no output schema, the description covers what the default call returns (the enumerated operation set), what operation_id expands to, and the beta/free status. Nothing material to calling it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in structured form, and the description's note about operation_id largely restates what the schema says. The country parameter is not addressed at all in the description beyond the EU27 mention, so no real value is added over the schema.

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 specific verb + resource ('List Mandate operations') and then enumerates every operation id with a one-line gloss, so an agent knows exactly what the catalog contains. It does not, however, distinguish this from close siblings such as list_actions or list_templates, leaving the boundary between the two catalog tools implicit.

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

Usage Guidelines3/5

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

The description implies a two-mode usage (call bare to browse, pass operation_id to inspect one operation) but never says so explicitly and gives no when-to-use / when-not-to-use or pointer to order_operation or get_formation_guide as the next step. Usage has to be inferred from the schema and the sentence about operation_id.

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.

Resources