Skip to main content
Glama

Whizbrew

Get data

call_tool
Read-only

Runs one catalogue tool that reads data. A call is charged the tool's listed price only when it is a hit (it answered with data). A miss (answered, nothing there) and a failed call are not charged. The answer's meta says which: outcome, price_micros (what was charged) and balance_micros.

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

Input Schema

NameRequiredDescriptionDefault
toolYesTool name from search_tools, e.g. tiktok.profile
argumentsNoThe tool's input, as describe_tools shows it
max_age_sNoOptional. The oldest answer you take, in seconds, for a tool whose repeat calls are answered from the cache (describe_tools shows cache for those). 0 = always read at the source, at the full price. Without it the tool's own maximum age applies; meta.cached, fetched_at and age_s say what you got
idempotency_keyNoOptional. Your own name for this call (up to 200 characters). When a call that was charged is sent again with the same key, tool and arguments within 24 hours, the stored answer comes back free (meta.replay). Use it when you send a call again after a timeout
max_cost_microsNoOptional. The most this call may cost, in millionths of a dollar (1000000 = $1). A tool priced above it is refused before it runs, free, with its price in the error

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the billing model (charged only on a hit, free on a miss or failure), the meta fields that report outcome, price_micros and balance_micros, cost refusal via max_cost_micros, and free replay via idempotency_key. That is precisely the behavior an agent needs before spending money on a read.

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?

Three front-loaded sentences: what it does, then when it costs money, then where to look in the answer. No filler. Minor inefficiency in that the billing rule is restated across two sentences (hit vs miss and failed).

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?

There is no output schema, so the description correctly explains the `meta` fields an agent needs to interpret the response, and it covers cost risk for an open-world tool. It does not describe the returned data payload itself or the error shape beyond a price refusal, which leaves a small gap for a tool with five parameters.

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 coverage is 100% and each parameter already carries a description, so the schema does the heavy lifting and a 3 is the baseline. The prose adds billing context that helps interpret the result but adds no parameter syntax or format meaning 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?

It states a specific verb and resource: runs one catalogue tool that reads data, with the tool named via the required `tool` argument. It is clear what the tool does, but it never contrasts itself with the sibling `request_tool`, so the agent cannot tell from the description alone which of the two executes a catalogue tool.

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: the schema points to `search_tools` for the tool name and `describe_tools` for arguments, and the description implies this is the execution step. There is no explicit when-to-use or when-not-to-use statement, and no mention of when `request_tool` or `get_quote` would be preferred.

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