Skip to main content
Glama

Vertrags-PDF herunterladen

download_contract_pdf
Read-only

PDF eines Mietvertrags (ausgestellt: das eingefrorene PDF; Entwurf: Vorschau mit ENTWURF). Liefert die Datei base64-kodiert.

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": {
      "id": "<id>"
    },
    "name": "download_contract_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVertrags-ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds real behavioral context beyond that: an issued contract yields the frozen PDF, a draft yields a preview stamped ENTWURF, and the payload is base64-encoded rather than a raw file—useful details an agent cannot get from the schema.

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?

Two compact sentences with no filler, and the state-dependent behavior is front-loaded before the return-format note. Every clause carries information.

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 one-parameter read tool with no output schema, the description covers the essential unknowns: what file variant comes back and how it is encoded. It does not mention failure behavior (e.g., missing contract or missing PDF) or size/rate limits, but nothing critical to a correct call is absent.

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% for the single parameter (id: 'Vertrags-ID'), so the schema already carries the parameter meaning. The description adds nothing about the id's format or source (e.g., from list_contracts), so the baseline 3 applies.

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—returns the PDF of a rental contract—and the name/schema confirm it targets a contract by id. It distinguishes the two content variants (issued vs. draft), though it never explains how it differs from the sibling download_document_pdf, which is the most likely point of confusion.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no reference to alternatives such as download_document_pdf or get_contract. The agent must infer from the tool name alone which of the two download tools to pick.

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