Skip to main content
Glama

Price a research report

research_price
Read-onlyIdempotent

Fits when the user asks for a written report on a question, before it is approved. Returns the price of one report at each depth (quick, standard and deep) in dollars and in cents, and how many parts of the question each depth researches. A report is charged once, when it is delivered; a run that fails, is cancelled or reads no page is not charged. Nothing runs and nothing is charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "research_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoquick, standard or deep. Without it, the price of each depth.

Output Schema

NameRequiredDescriptionDefault
pricesNoOne price for each depth.
chargedNoWhen the price is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "The price of one report at each depth, charged once on delivery.",
      +  "properties": {
      +    "charged": {
      +      "description": "When the price is charged.",
      +      "type": "string"
      +    },
      +    "prices": {
      +      "description": "One price for each depth.",
      +      "items": {},
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description is not obligated to establish safety. It still adds real value with the billing model: charged once at delivery, and a failed, cancelled or zero-page run is not charged. The only gap is whether prices are stable over time or vary by account.

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?

Front-loads the triggering condition, then the return shape, then the billing caveats, with no filler. The final sentence ('Nothing runs and nothing is charged.') partially restates the charging rule already given one sentence earlier, a minor redundancy.

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?

The tool has one optional enum parameter, full annotations and an output schema, so the description only needs to cover purpose, timing and cost semantics, all of which it does. Nothing an agent needs in order to call it or interpret the price is missing.

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% and the enum's own description already explains the omit-to-get-all behavior, so the baseline is 3. The description goes further by saying what each depth buys ('how many parts of the question each depth researches') and that prices come back in both dollars and cents, which adds meaning beyond the raw enum values.

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 ('Returns the price of one report at each depth') and scopes it to a moment ('when the user asks for a written report on a question, before it is approved'). The closing line 'Nothing runs and nothing is charged' separates it from the execution siblings like start_research without naming them.

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?

Gives a clear triggering condition (user asks for a written report, before approval) and a clear non-effect statement, which implies this is the pre-flight check rather than the run. It does not explicitly point to the tool that actually starts the research once the price is known, leaving that routing to be inferred.

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.