Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

get sample response

get_sample
Read-only

Show a real sample response for any tool before paying (e.g. pretrade_check). Free.

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

Input Schema

NameRequiredDescriptionDefault
toolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value by disclosing cost behavior ('Free', 'before paying'), but leaves open whether the sample is live or canned and whether there are rate limits or call quotas.

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?

One sentence plus the fragment 'Free.' — front-loaded with the action and cost benefit, zero wasted words. Slightly clipped to the point of being terse about the return value.

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 simple one-parameter read-only tool with no output schema, the description covers purpose and cost but says nothing about what the sample response looks like or how large it is, which matters since previewing output is the entire point of the tool.

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?

Schema description coverage is 0%, so the description carries weight; it does imply the single parameter selects which tool's response to sample. However, the enum is self-documenting and the description adds no detail on format (exact name vs. alias) beyond that implication.

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?

States a specific verb and resource — show a real sample response for a tool — which is clearly distinct from the sibling tools it previews. The example (pretrade_check) anchors what 'any tool' means, though it doesn't explicitly say it covers every sibling.

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?

'Before paying' gives a concrete decision point: preview the response shape prior to invoking a paid tool. It does not state when-not to use it (e.g., after you already know the shape) or note alternatives, but the trigger context 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