RealtimeAPI.ai

get_sample

Read-only

Free trimmed sample of an endpoint's real response from the probe's cached copy (no key, no payment): see the data shape before paying. Works for results discover marks sample: true.

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

Name	Required	Description	Default
`url`	No	Gateway URL, e.g. https://api.realtimeapi.ai/v1/cryptodata/market-health
`tool`	No	Tool name from discover, e.g. "cryptodata_market-health"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the response is free, requires no key or payment, is trimmed, and comes from a cached probe copy rather than a live call. It does not explain what is trimmed or how stale the cache may be.

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?

The description is short and front-loads the free-sample purpose before the applicability condition. The phrase 'Works for results discover marks sample: true' is slightly awkward but still understandable.

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 simple two-parameter read-only preview tool with no output schema, the description covers the essential context: it is free, cached, trimmed, and only valid for discover results marked sample: true. Minor gaps remain around what trimming means and what happens when no sample exists.

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?

The input schema already documents both url and tool at 100% coverage, including examples and source from discover. The description reinforces the discover relationship with the sample: true condition but adds little parameter-specific detail beyond the schema.

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 states a specific resource: a free, trimmed sample of an endpoint's real response from the probe's cached copy. It distinguishes the tool from paid endpoint calls by framing it as seeing the data shape before paying, though it does not explicitly name the paid sibling tool.

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 gives a clear use case, previewing data shape before paying, and a concrete applicability condition: results that discover marks sample: true. It does not explicitly state when not to use it or name alternatives such as call_feed.

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

All RealtimeAPI.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?