Skip to main content
Glama

x402 Tool Shop

Free sample answer

free_sample
Read-only

Free: a real answer from any tool for its example input, so you can see the output before paying. tool is one of: clinical_calculator, csv_preflight, dns_lookup, email_check, event_weather, sanctions_screen, weather_forecast.

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": {
      "tool": "<tool>"
    },
    "name": "free_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe tool name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's added value is the billing model (free) and the important behavioral detail that the call is driven by the tool's own example input rather than caller-supplied data. It stops short of disclosing sample limits, quota, or whether the sample output differs from a paid call.

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?

Compact and front-loaded, leading with 'Free:' and the effect, then the valid values. The construction is slightly compressed ('tool is one of: ...') and could read more cleanly, but no sentence is wasted.

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 one-parameter tool with no output schema, the description conveys enough: it says the result is a real answer from the chosen tool on its example input, which sets expectations about return shape. It omits any note on error behavior when an invalid tool name is passed, which would have closed the last gap.

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

Parameters5/5

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

Schema coverage is 100%, but the schema only documents 'tool' as 'The tool name' and defines no enum. The description supplies the actual valid values (clinical_calculator, csv_preflight, dns_lookup, email_check, event_weather, sanctions_screen, weather_forecast), which is meaning the schema does not provide and is required to call the tool successfully.

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?

States a specific action and resource: it returns a real answer from a named tool using that tool's example input, so an agent can preview output before paying. The enumerated value list plus the 'see the output before paying' framing makes clear this is a meta/preview tool, not one of the domain siblings.

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?

The phrase 'so you can see the output before paying' gives a clear context for when to reach for it: before committing to a paid call. It does not state any exclusions (e.g. whether repeated samples are allowed or whether it should be avoided for production use), so guidance is clear but not exhaustive.

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