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

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

download_order_confirmation_pdf

Read-only

Download a PDF of an order confirmation by providing its ID.

Instructions

Gets pdf of specified order confirmation

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": {
      "order_confirmation_id": "<order_confirmation_id>"
    },
    "name": "download_order_confirmation_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_confirmation_idYesorder confirmation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations provide readOnlyHint=true and destructiveHint=false, making it clear the tool is safe. However, the description adds no additional behavioral context (e.g., error handling, output format beyond 'pdf', or whether it returns binary data).

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?

Description is a single, short sentence that conveys the core purpose. It could be slightly expanded with usage notes while remaining concise, but it is not verbose.

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 one-parameter tool with good annotations, the description is minimally adequate. It lacks context about return value (PDF binary), error scenarios, and usage context, but given the simplicity, it meets basic needs.

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?

The single parameter order_confirmation_id is fully described in the input schema (type integer, description). Description adds no extra meaning, but schema coverage is 100%, so baseline score 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?

Description clearly states 'Gets pdf of specified order confirmation', specifying both the action (get pdf) and the resource (order confirmation). This distinguishes it from siblings like get_order_confirmation (returns JSON) and other download_pdf tools for different document types.

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?

Description lacks any guidance on when to use this tool vs alternatives (e.g., get_order_confirmation, get_order_confirmation_preview, send_order_confirmation_by_email). No prerequisites or conditions are mentioned.

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