Skip to main content
Glama
Sign In
mcp-server-smallinvoice

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

download_letter_pdf

Read-only

Retrieve a PDF of a specific letter by providing its unique ID. Use this tool to download letter documents directly from smallinvoice.

Instructions

Gets pdf of specified letter

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": {
      "letter_id": "<letter_id>"
    },
    "name": "download_letter_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
letter_idYesletter ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds no additional behavioral context beyond what annotations convey, such as permissions or error handling.

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 a single sentence with no wasted words. It is concise and front-loaded with the key action and object.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is adequate but leaves ambiguity about the response format (e.g., binary PDF content). Some additional context would improve completeness.

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% for the single parameter 'letter_id', which is described as 'letter ID'. The description does not add any extra semantics or constraints beyond 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?

The description 'Gets pdf of specified letter' clearly indicates the tool retrieves a PDF for a letter. However, it could be more specific about the output format or differentiate from sibling tools like download_invoice_pdf.

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?

The description provides no guidance on when to use this tool vs alternatives (e.g., send_letter_by_email, get_letter_preview). It lacks any context about prerequisites or exclusions.

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

Deploy Server

Other Tools