Skip to main content
Glama

estimate_cost

Calculate the Reach Dog token cost for a single title, research, or content request before you submit it, so you can plan usage and avoid unexpected charges.

Instructions

Estimate one title, research or content request in Reach Dog tokens.

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

Input Schema

NameRequiredDescriptionDefault
parametersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not say whether estimation is free/side-effect-free, whether it consumes tokens itself, whether results are cached or time-sensitive, or what the response contains — all material for a budgeting tool.

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?

One front-loaded sentence with no filler and no redundancy. However, the brevity is achieved by omitting essential detail rather than by efficient phrasing, so it sits just below top marks.

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

Completeness2/5

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

With no annotations, no output schema, and an opaque single array parameter, the description would need to do much more work. It fails to explain the input encoding or the nature of the returned estimate, so an agent cannot call this tool confidently without experimentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'parameters' array, and the description adds essentially nothing about it — it never explains whether entries are parameter names, key/value strings, or natural-language request fragments. The ordinal constraint on ordering is likewise unaddressed, leaving the caller guessing at a required input.

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?

States a concrete verb (estimate) and unit of output (Reach Dog tokens) applied to three named request types (title, research, content). An agent can grasp the general function, though the description never differentiates it from siblings like research_market or generate_content, which also take request-like inputs.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives such as research_market or generate_content. The agent must infer that this is a pre-flight cost check before committing to one of those operations.

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