Skip to main content
Glama

A2A Defense & Monetization Gateway

calculate_service_quote

Calcula la cotización formal en créditos según complejidad de cómputo, tokens y riesgo.

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": {
      "service_type": "<service_type>"
    },
    "name": "calculate_service_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_typeYes
estimated_tokensNo
estimated_compute_msNo
adversarial_risk_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether calculating a quote consumes or reserves credits, whether results are deterministic, whether there are rate limits or auth requirements, or what the effect of an adversarial risk score is. For a commercial/pricing tool with zero annotation coverage, that is a substantial gap.

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?

A single front-loaded sentence with no filler; every clause maps to a pricing factor. It is efficient, though its brevity contributes to the missing usage and behavioral information assessed elsewhere.

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?

For a four-parameter quoting tool with no annotations, no output schema, and no schema descriptions, the definition is too thin. An agent cannot tell what the response contains (price only? breakdown?), whether quotes expire, or how defaults of 500 tokens / 50 ms / 0.05 risk affect the price.

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 0%, so the description must compensate. It maps conceptually onto three of the four parameters (compute complexity → estimated_compute_ms, tokens → estimated_tokens, risk → adversarial_risk_score), which is genuinely useful. However it gives no units, no default expectations, and no indication of valid service_type values, leaving key semantic gaps.

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 description states a specific verb and resource: it calculates a formal quote denominated in credits, and it names the driving factors (compute complexity, tokens, risk). An agent can tell this is a pricing/estimation tool. It stops short of distinguishing itself from credit-related siblings such as redeem_credits_for_sats or execute_sandboxed_computation.

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 guidance on when to call this versus alternatives, no prerequisites, and no statement of whether the quote is advisory or binding. The agent must infer usage entirely from the tool name and factor list.

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