Skip to main content
Glama

Tribute Paper

Get prices

get_pricing
Read-onlyIdempotent

Tribute Paper's current prices, in US dollars, British pounds, Canadian dollars or Australian dollars (all four if no currency is given). Always use this rather than stating or guessing a price. It is free to design; there is one payment, only to publish, with nothing added at checkout.

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

Input Schema

NameRequiredDescriptionDefault
currencyNoUSD, GBP, CAD or AUD. Leave out for all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the default-return behavior (all four currencies when omitted) plus the underlying pricing model — free to design, one payment at publish, nothing added at checkout — which lets the agent answer follow-ups without another call. It stops short of stating price freshness or volatility.

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?

Three short sentences with the resource and currency scope front-loaded and the usage directive second. The final sentence about the payment model is technically about pricing policy rather than the tool, but it earns its place by pre-empting a common follow-up question.

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

Completeness4/5

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

For a single optional enum parameter with no output schema, the description covers the input default and the pricing context well. It does not describe the shape of the returned data (e.g. a per-currency price map) or whether prices can change between calls, which would fully close the gap.

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% and the enum already enumerates USD/GBP/CAD/AUD with the 'leave out for all four' default. The description restates the same default in prose and spells out currency names, adding no syntax or format meaning beyond the schema. Baseline 3 applies.

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?

The description names a specific resource (Tribute Paper's current prices) and its scope (four currencies, all four returned when no currency is given), which is unambiguous against siblings like get_design or get_reading. An agent can tell exactly what data comes back without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit standing directive: 'Always use this rather than stating or guessing a price.' This is stronger than typical context-setting because it names the failure mode it prevents (hallucinated prices) and closes off the alternative behavior entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources