Skip to main content
Glama
Sign In

Mandate Office

by com.mandateoffice
OverviewDiscussionsAdmin

get_template

Read-only

Get one standard template by id (fields, clauses or markdown body metadata, legal_basis with [K] sources). Same as GET /api/templates/{id}. Partner-only templates need the partner key. Free, read-only.

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": {
      "template_id": "<template_id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesTemplate id from list_templates, e.g. es_auction_poa_v2 or es_contrato_arras_v1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavior beyond that: partner-only templates require the partner key, access is free, and the call maps to GET /api/templates/{id}. It still does not describe error behavior for missing or unauthorized templates, but it is transparent for a simple read operation.

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

Conciseness5/5

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

The description is front-loaded, uses only three short sentences, and wastes no words. Each sentence adds relevant context: the operation, endpoint equivalence, and partner-key/access conditions.

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

Completeness4/5

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

For a simple one-parameter read tool with no output schema, the description does a good job explaining what is returned: fields, clauses or markdown body metadata, and legal_basis with [K] sources. It could be more complete by mentioning error or missing-template behavior, but it covers the essential context.

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 coverage is 100%, and the schema already explains that template_id comes from list_templates with examples. The description adds only "by id" and does not provide additional format or constraint details beyond the schema, so baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb ("Get one"), resource ("standard template"), selector ("by id"), and even the returned content categories. This clearly distinguishes it from list_templates, which enumerates templates, and fill_template, which populates them.

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?

It gives the implied use case of fetching a single template when an id is available and notes that partner-only templates require the partner key. It does not explicitly name list_templates as the source of ids or explain when to use fill_template instead, so the guidance remains implicit rather than explicit.

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

All Mandate Office toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources