Skip to main content
Glama
Sign In
Agent Data Tools

Agent Data Tools

by Nutshell2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

call_tool

Read-only

Runs any agent-data-tools tool by name with your inputs as arguments, charging only on success. Confirm the tool name and inputs first to avoid refused, uncharged calls.

Instructions

Run one of this service's tools by name. Costs that tool's own price per successful call (most $0.01; tool_details and find_tool show it); a failed call costs nothing, and tools marked inFreeCalls run free while the caller has free calls left. Pass the tool's inputs as "arguments". If you do not know the name or the inputs, call find_tool or tool_details first: a wrong name or a missing input is refused before anything is charged. A tool that costs more than $0.10 a call (find_tool marks it needsMaxPrice) runs only when you pass that price as "max_price"; without it the call is refused, uncharged, and the refusal states the price.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe tool's name from find_tool, for example weather_forecast
argumentsNoThe tool's inputs as an object, for example {"city": "Paris"}. See tool_details for a tool's inputs
max_priceNoOnly for a tool that costs more than $0.10 a call: the most this call may cost, for example "$1.00". Leave it out for every other tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: per-call pricing charged only on success, free calls when the caller has quota, and pre-charge refusal for a wrong name or missing input. The refusal semantics for max_price (refused, uncharged, price stated in the refusal) are exactly the kind of detail an agent cannot infer. The one gap is that it never says the proxy inherits the target tool's side effects, which sits awkwardly beside readOnlyHint=true/destructiveHint=false on a tool that can execute arbitrary operations.

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?

Roughly 110 words in a single front-loaded block that opens with the action before the pricing detail. The pricing sentence is dense and carries two semicolon-separated clauses, but every clause adds decision-relevant information rather than repeating the schema.

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?

Covers the two things an agent most needs for a 3-parameter proxy: how to supply inputs and how to avoid an uncharged refusal. With no output schema, however, it never indicates what the response looks like — whether the target tool's output is returned directly or wrapped — which is the main remaining unknown.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining that 'arguments' is the target tool's own input object and by framing max_price as a guard that only applies above the $0.10 threshold. It stops short of saying what happens to max_price when a tool is under the threshold (ignored vs. rejected).

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 verb and resource — run one of the service's tools by name — and implicitly positions itself against the discovery siblings find_tool and tool_details by naming them as the prerequisite step. An agent can tell execution apart from discovery without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: if you do not know the name or the inputs, call find_tool or tool_details first. It also gives a conditional for the max_price parameter tied to a concrete threshold ($0.10) and the needsMaxPrice marker, so both the when-to-use and the when-to-omit cases are covered.

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

Deploy Server

Other Tools