Skip to main content
Glama

Whizbrew

Price a task

get_quote
Read-only

A free quote before you spend: which tools do a goal, the calls in order, the price per call and for the quantity you state, and the cash needed beyond the balance. Never spends. The answer ends with next: one step you can read to your human.

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

Input Schema

NameRequiredDescriptionDefault
goalYesWhat you want to do, in plain words
quantityNoHow many calls you expect to make
budget_usdNoOptional. What your human allows for this task, in US dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this with 'Never spends.' It goes further by disclosing the response shape, including a trailing `next` field intended to be surfaced to a human, which is context the annotations cannot convey.

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?

Two dense sentences, roughly fifty words, with the core promise ('free quote before you spend') front-loaded and the response highlights immediately after. No filler or repetition.

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?

With no output schema, the description carries the burden of explaining return values, and it does so well enough for an agent to know it will get a plan, a price breakdown, and a `next` step. Minor gaps remain, such as what happens when budget_usd is too low or how long a quote stays valid.

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, but the description adds real meaning: quantity drives the quoted price, and budget_usd connects to the 'cash needed beyond the balance' figure. It clarifies how the parameters shape the output rather than just restating them.

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?

Names a specific resource (a quote) and enumerates exactly what the quote contains: which tools reach the goal, the ordered calls, per-call and quantity pricing, and cash needed beyond balance. 'Never spends' cleanly separates it from a sibling like call_tool without needing to name it.

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?

'A free quote before you spend' gives a clear trigger point in the workflow, implying it precedes actual execution. It stops short of naming the alternative tool or stating exclusions, so the when-not guidance is inferred rather than explicit.

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