Skip to main content
Glama

ai_modeling_quote

Read-only

Estimate credit costs for operations from reviewed evidence before discounts, blocking submission when prices are unknown so agents can validate quotes before proceeding.

Instructions

Estimate credits before discounts from reviewed current evidence. Unknown prices block submission. Estimates are not an upstream spending cap.

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

Input Schema

NameRequiredDescriptionDefault
operationYes
parametersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the figure is pre-discount, missing prices block submission rather than producing a partial estimate, and the number is advisory rather than an upstream spending cap. Those caveats are exactly the kind of context annotations cannot carry. It does not say whether the call is billed or how stale evidence is handled.

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?

Three short sentences, front-loaded with the core action and with no redundant restatement of the tool name. 'From reviewed current evidence' is slightly opaque phrasing for a short description. Every sentence still carries a distinct caveat.

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

Completeness3/5

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

There is no output schema, so the description should explain what comes back, and it only implies a credit figure. For a tool with 0% documented parameters, a 29-member enum, and arbitrary nested keys, the description says nothing about the required input shape. The behavioral caveats are solid, but the input side is left entirely to the schema.

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 description coverage is 0% and the schema is a nested object with free-form properties plus a 29-value operation enum, so the description must compensate and does not. It never mentions the operation field, which enum values are valid, or what keys belong inside 'parameters' for a given operation. The only weak signal is the word 'submission,' which is not tied to a parameter.

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?

The opening sentence states a specific verb and resource: estimate credits, before discounts, based on reviewed current evidence. It is distinguishable from siblings like ai_modeling_balance or ai_modeling_account_status, which report balances rather than quoting a cost. It stops short of saying the estimate is scoped to a modeling operation, which leaves a small ambiguity.

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?

No explicit when-to-use guidance is given. 'Unknown prices block submission' hints that the tool is a pre-submission check, but the description never names an alternative or a condition such as 'call before refine_submit/export to preview cost.' The agent must infer the workflow placement on its own.

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

Deploy Server

Other Tools