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

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_exchange_rates

Read-only

Retrieve a list of currency exchange rates with optional search, filter, and pagination.

Instructions

Returns list of currency exchange rates

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

Input Schema

NameRequiredDescriptionDefault
qNoValue for full text search
filterNoFilter expression (JSON)
limitNoLimits the number of items returned. Number in a range [1-200]
offsetNoOffset of the first item to return. The offset of the initial item is 0.

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's claim of returning a list is consistent. No additional behavioral traits are disclosed, but with annotations covering the safety profile, a score of 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, front-loading the core purpose. It could be slightly improved by adding a second sentence for context, but it is not overly verbose.

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?

Despite good schema coverage and annotations, the description omits information about return format, pagination behavior, or common use cases. For a 4-parameter tool with no output schema, the description is insufficiently complete.

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 description coverage is 100%, with each parameter documented in the schema. The description adds no extra meaning to parameters, so a baseline of 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 clearly states the tool returns a list of currency exchange rates, using a specific verb and resource. However, it does not differentiate from other list tools or specify what kind of rates are returned, so it misses the highest score.

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?

No guidance is provided on when to use this tool versus alternatives like get_exchange_rate or other list tools. The description lacks context on filtering or searching, leaving the agent without decision support.

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