Skip to main content
Glama

get_sample

Free. Full sample responses for 3 large banks, to check the data before paying.

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_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description has to carry the full burden, and it discloses the two facts that matter most for a sample endpoint: it costs nothing ('Free') and returns data for only 3 large banks (limited scope). It does not say whether the payload is static or rate-limited, but the safety and cost profile are effectively communicated.

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

Conciseness5/5

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

Two short fragments, front-loaded with the 'Free' qualifier, with zero filler. Every clause adds information: cost, scope, content, and purpose.

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 zero-parameter, no-output-schema preview tool, a sentence that names the payload ('full sample responses') and its coverage (3 large banks) is close to sufficient. An agent still has to call it to learn the exact payload shape, which keeps it just short of a 5.

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 input schema defines no parameters, so the baseline of 4 applies. The description correctly exposes no parameter semantics to document, and therefore adds no misleading detail.

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 names a specific resource — full sample responses for 3 large banks — and the 'sample' framing separates it from real query siblings like get_bank_metrics or screen_banks. The verb is implicit rather than stated, but the name plus the phrase 'Full sample responses' leaves no real ambiguity about what comes back.

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?

'To check the data before paying' gives a clear use context: trial/preview ahead of purchase. It does not name an alternative tool or state when not to call it, and it never explicitly says a different endpoint should be used once real data is needed — the guidance is implied rather than spelled out.

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