Briefverzenden — fysieke post

Document aanleveren

document

Levert de PDF aan die verstuurd moet worden, als base64 of als publieke https-URL. Geeft een verwijzing terug die je aan bestellen meegeeft, plus het getelde aantal pagina’s.

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": "document"
  }
}

Input Schema

Name	Required	Description	Default
`fileUrl`	No	Publieke https-URL waar de PDF staat.
`fileBase64`	No	De PDF als base64.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that the tool returns a reference and a page count, and specifies the input methods (base64 or HTTPS URL). This adds meaningful behavioral detail beyond the annotations, though it doesn't cover edge cases like both parameters being provided or error behavior.

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 extremely concise—two sentences with the main action upfront and supporting details following. Every word contributes value, with no redundancy.

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?

The description covers the core workflow: provide a PDF (as base64 or URL) and receive a reference for 'bestellen' plus page count. It does not explicitly state the requirement for exactly one of the two parameters, but the overall intent and integration with the sibling tool are clear.

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%, giving a baseline of 3. The description adds the crucial 'of' (or) relationship between fileBase64 and fileUrl, clarifying that they are alternatives, which is not explicit in the schema.

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 uses the specific verb 'Levert' (delivers) and clearly identifies the resource (PDF) and its purpose (to be sent). It distinguishes itself from siblings by explaining that it returns a reference for 'bestellen' and the counted pages.

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?

The description gives clear context for when to use the tool: 'Geeft een verwijzing terug die je aan bestellen meegeeft' (returns a reference to pass to bestellen). It doesn't explicitly mention exclusions or alternatives, but it uniquely handles document preparation among siblings.

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

All Briefverzenden — fysieke post tools Inspect

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

Need Help?