Skip to main content
Glama
Sign In

Andru

by io.github.geter-andru
OverviewDiscussionsAdmin

Get the price of a call

quote
Read-only

Use this when the person asks what a call would cost. Send the tool name and its arguments. Returns the price, whether today's free calls cover it, the wallet balance, how much this key can still spend without asking, and a quote_id that holds the price for 30 minutes. Pass quote_id with the call to pay the quoted 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": {
      "tool": "<tool>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe tool you plan to call, e.g. get_pre_brief.
argumentsNoThe arguments you plan to send with it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description stays consistent while adding substantive behavioral detail beyond what annotations carry: what the response includes (price, free-call coverage, wallet balance, remaining key spend limit) and the 30-minute quote validity window. The quote_id handoff is the key behavioral fact an agent needs and it is stated plainly.

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?

Four short sentences, each doing distinct work: trigger, input, return contents, quote validity. The trigger and the payoff instruction are front- and back-loaded where an agent will see them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden and does so fully — itemizing the price, free-call coverage, wallet balance, spend cap, and quote_id with its expiry. There is no material gap for a two-parameter read-only pricing 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 100%, so both parameters (tool, arguments) are already documented, and the description only restates 'send the tool name and its arguments'. Baseline 3 applies; the quote_id handoff is a cross-tool instruction rather than added meaning for these two parameters.

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 ('what a call would cost') and frames it around the triggering situation. It is clearly distinguishable from data-retrieval siblings like get_pre_brief or whoami, which it names implicitly as the tools being priced.

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?

Explicit trigger ('when the person asks what a call would cost'), explicit input instruction ('send the tool name and its arguments'), and explicit follow-up ('pass quote_id with the call to pay the quoted price'). No when-not-to-use case or named alternative is given, which keeps it short of a 5.

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

All Andru toolsInspect
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