Skip to main content
Glama

Price covers

quote_cover
Read-onlyIdempotent

What a round of 1 to 4 covers costs, and a redraw credits: what a round of count covers costs now (the direction once, each cover on top); redraw_credits: redrawing one cover with a note. Tell the user before make_cover or redraw_cover, and send the same credits.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many covers (1 to 4, default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the 'costs' framing is consistent with a non-mutating estimate. The description adds that the returned credits should be passed along to the subsequent make/redraw call, which is behavior beyond annotations. It doesn't explain the credit model, price stability, or the response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but badly malformed: 'what a round of count covers costs now (the direction once, each cover on top)' is not parseable English, and the 'what a round of ... covers costs' clause is effectively repeated. The single useful instruction (tell the user before make_cover/redraw_cover) is buried at the end rather than front-loaded.

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 one-optional-parameter read-only quote tool with annotations covering safety and full schema documentation, the description supplies the essential flow: quote before make/redraw and pass credits along. It omits pricing dimensions (currency, credit expiry, what the response contains), but with no output schema some return-value silence is acceptable. Adequate with noticeable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and count is already documented as '1 to 4, default 1'. The description reinforces the range and adds meaning by implying per-cover pricing ('each cover on top'), i.e. the total is computed per cover rather than as a flat price. That is a genuine semantic contribution, though limited to one parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening 'What a round of 1 to 4 covers costs' conveys a pricing/quoting intent for covers, and the title 'Price covers' helps, but the sentence is garbled ('what a round of count covers costs now (the direction once, each cover on top)') and never states a clean verb-resource pair. An agent can infer it's a cost/credit estimator but the grammar obscures the purpose.

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

Usage Guidelines4/5

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

It explicitly routes usage: 'Tell the user before make_cover or redraw_cover, and send the same credits.' That names the two sibling tools it precedes and instructs the agent to surface the quote to the user first. It gives no when-not guidance and ignores other quote siblings like quote_canvas, but the primary workflow routing is clear.

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