Skip to main content
Glama

Smarty Pants

Estimate cost

estimate_cost
Read-onlyIdempotent

Estimate the US dollar cost of running a Smarty Pants model for a given number of input and output tokens and requests. Uses the published per-token prices. No sign-in needed.

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": {
      "model": "<model>",
      "input_tokens": "<input_tokens>",
      "output_tokens": "<output_tokens>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel id from list_models, for example smartypants/qwen3.5-9b
requestsNoNumber of requests (default 1)
input_tokensYesPrompt tokens per request
output_tokensYesCompletion tokens per request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, disclosing the pricing basis ('published per-token prices') and that no authentication is required. It stops short of stating rounding, currency-conversion, or whether prices reflect current vs. cached rates.

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?

Three short sentences: what it computes, what prices it uses, what auth it needs. The core purpose is front-loaded and every sentence carries distinct information with no filler.

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?

For a simple read-only calculator with no output schema and full schema coverage, this is nearly sufficient — the agent knows the inputs, the pricing source, and the access requirement. The only real gap is whether the estimate is a per-request or total figure and how rounding is applied.

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 all four parameters (model, input_tokens, output_tokens, requests) are already documented with types, bounds, and per-request semantics. The description restates the same inputs without adding format, unit, or interaction detail. Baseline 3 is appropriate.

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 ('Estimate the US dollar cost of running a Smarty Pants model') plus the exact inputs that drive it (input tokens, output tokens, requests). This is clearly distinguishable from siblings like list_models or request_model, which handle discovery and execution rather than pricing.

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

Usage Guidelines3/5

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

The description implies this is a pre-flight pricing check but never says when to call it versus alternatives, nor what to do with the result. 'No sign-in needed' is a useful prerequisite note, but it is the only contextual guidance offered. The model-id reference to list_models lives in the schema, not the description.

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