Skip to main content
Glama

Mandate Office

by com.mandateoffice
OverviewDiscussionsAdmin

fill_template

Read-only

Fill a standard template. Default output on MCP: content[0] = the bilingual document text, content[1] = short summary; structuredContent = metadata (status, warnings, 1-hour DOCX/PDF download links with a random id; the fill data is kept encrypted on the server for 1 hour, never in the URL); request formats docx/pdf for base64. Optional auction_id (SUB-... or BOE-B-...) prefills empty fields from public BOE data (read only, nothing is submitted); it must match fields.auction_id / fields.boe_announcement_id if those are given (else error auction_id_conflict). Incomplete fills come back with status draft_incomplete and a DRAFT / DO NOT SIGN watermark. No case assessment, no legal advice; the notary drafts the final deed. Partner-only templates need the partner key.

Input Schema

NameRequiredDescriptionDefault
lotNoOptional lot number for prefill.
langNoSecond language next to the base language: en (default), de, it, fr (as listed in the template).
fieldsNoField values; principals is an array of {name, kind natural|legal, id_type, id_number, nationality (ISO alpha-2, natural persons), country (ISO alpha-2, country of incorporation) and registry (companies), address, share_percent, signatory, signatory_basis}.
formatsNoMCP default [text, links]. docx/pdf add base64 files. REST default [text, docx, pdf, links].
auction_idNoOptional SUB-... or BOE-B-... to prefill from public data.
template_idYesTemplate id from list_templates or quote_action, e.g. es_auction_poa_v2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial context beyond the readOnlyHint/openWorldHint annotations: exact output channels (content[0], content[1], structuredContent), 1-hour encrypted server retention, random download links, auction_id conflict errors, draft status with a DRAFT / DO NOT SIGN watermark, and the no-legal-advice disclaimer.

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?

The description is front-loaded with purpose and every clause carries useful information, but the long single-paragraph format with semicolons and parentheticals makes it denser than ideal.

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 complex tool with six parameters, nested objects, and no output schema, the description fully explains return structure, storage lifetime, edge-case statuses, error codes, and access restrictions. Nothing essential is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for auction_id, including accepted formats (SUB-... / BOE-B-...), prefill behavior, read-only nature, and the auction_id_conflict error condition.

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?

The description states a specific verb and resource ('Fill a standard template') and immediately clarifies output behavior. It does not explicitly differentiate itself from siblings like quote_action or list_templates, but the purpose is unambiguous.

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 useful conditional guidance for auction_id prefill, partner-only templates, and incomplete fills, but never states when to choose fill_template over quote_action or list_templates beyond mentioning template_id sources in the schema.

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