Skip to main content
Glama

Get pricing

get_pricing
Read-onlyIdempotent

Prices for a preview, a pack and a re-render, in USDC on Base. Free.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 covered structurally. The description adds genuinely new facts: the currency (USDC on Base) and that the call is free. It does not say whether prices are static or time-sensitive, nor what "re-render" refers to.

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?

A single short sentence with the priced items front-loaded and the currency qualifier after them; nothing is padding. The extreme terseness leaves terms like "re-render" and "pack" unexplained, but no sentence is wasted.

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 zero-parameter read with rich annotations, the essentials (what is priced, in what currency, at no cost) are present. However, with no output schema, the description carries the burden of hinting at the return shape and does not indicate whether the response is a single price or a per-item breakdown.

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?

The tool takes zero parameters and the description correctly introduces no parameter discussion, so there is nothing to mis-describe. Baseline for a parameterless tool applies.

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?

"Prices for a preview, a pack and a re-render, in USDC on Base" states a specific resource (price list) and enumerates the three priced items plus the currency/chain, which is far more concrete than the title alone. It is clear this returns cost data rather than content, implicitly distinguishing it from get_pack/get_preview, but it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the call to make before a purchase decision, and "Free" hints the call itself costs nothing. There is no explicit when-to-use statement, no mention of when it should be skipped, and no named alternative for related lookups.

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