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

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_order_confirmation_preview

Read-only

Retrieve a preview of an order confirmation by providing its ID, page number, and pixel width. Confirm layout and content before finalizing.

Instructions

Gets preview 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": "get_order_confirmation_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_confirmation_idYesorder confirmation ID
pageNopage number [1 .. pages amount]
sizeNowidth in pixels

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 (readOnlyHint=true) already indicate it is a read operation. The description adds no further behavioral context, such as the nature of the preview (e.g., image, HTML) or any constraints. It does not contradict annotations.

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 a single, concise sentence that front-loads the key action. It is not verbose, but could benefit from a slight expansion to improve clarity without losing conciseness.

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

Completeness2/5

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

Given three parameters (including page and size which hint at an image preview) and no output schema, the description lacks important context. It does not explain what the preview is or how the optional parameters affect the output, leaving gaps for an agent.

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 descriptions cover all parameters (e.g., 'page number [1 .. pages amount]', 'width in pixels'). The description adds no information beyond the schema, so baseline 3 is appropriate.

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 'Gets preview of specified order confirmation' with a clear verb ('Gets') and resource ('preview of order confirmation'). It distinguishes from sibling tools like get_invoice_preview and get_offer_preview by specifying the entity type.

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?

No explicit guidance on when to use this tool versus alternatives like get_order_confirmation or download_order_confirmation_pdf. Usage is implied but not clarified, leaving the agent to infer context from the tool name and sibling list.

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