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

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_offer_preview

Read-only

Retrieve a preview image of an offer by specifying its ID. Optionally set page number and image width to customize the preview.

Instructions

Gets preview of specified offer

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": {
      "offer_id": "<offer_id>"
    },
    "name": "get_offer_preview"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description only adds redundant context. It doesn't disclose additional behavioral traits like return format (URL, base64), resolution, or whether pagination (page, size) applies to the preview content. With annotations covering safety, a 3 is appropriate.

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 (5 words) with no fluff. It is front-loaded. However, it could be slightly expanded to clarify the preview format 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?

With no output schema, the description should explain what the preview returns (e.g., image, PDF, URL). It doesn't. The purpose of 'page' and 'size' parameters is ambiguous without context. Incomplete for a non-trivial tool.

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 input schema has 100% coverage with descriptions for all three parameters. The description adds no new semantics beyond the schema. Baseline 3 is correct.

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 preview of specified offer' clearly states the action (gets) and the resource (preview of an offer). It distinguishes from sibling tools like 'get_offer' (full details) and other preview tools (delivery note, invoice, etc.). However, it could be more explicit about what a preview entails.

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 versus alternatives like 'get_offer' or 'download_offer_pdf'. No mentions of context, exclusions, or prerequisites.

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