Skip to main content
Glama

dev_tools_calculate

[$x402 pago por llamada] Evalúa una expresión aritmética (+, -, *, /, ^, paréntesis y funciones básicas).

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": {
      "expression": "<expression>"
    },
    "name": "dev_tools_calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
expressionYesExpresión aritmética a evaluar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, and it delivers very little: it does not say what happens on malformed expressions, what numeric precision or type is returned, or that a call is billable/returns 402 without a payment header (only a cryptic tag hints at this). The one meaningful signal, that this endpoint is paid per call, is present but unexplained.

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 efficient sentence with the core purpose front-loaded, plus a short bracketed cost tag. Nothing is redundant, though the bracketed tag is terse enough to be slightly opaque.

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?

The tool is simple and has a fully described schema, so most of what an agent needs is present. However, with no annotations, no output schema, and a billed-per-call endpoint, the description should state the return type/precision and the 402 payment requirement explicitly rather than in a compressed tag.

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 coverage is 100%, so both parameters are already documented, including the x_payment 402 behavior. The description's operator enumeration adds some meaning about what the expression string may contain, but it adds nothing about the payment parameter beyond what the schema already states, so this lands at the baseline.

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+resource ("Evalúa una expresión aritmética") and enumerates the supported operator set, so the agent knows exactly what computation is performed. It does not explicitly contrast with numeric siblings like dev_tools_loan_calculate, dev_tools_statistics, or dev_tools_unit_convert, which is what keeps it from a 5.

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?

Usage is only implied by the operator list – an agent can infer this is a general-purpose expression evaluator rather than a domain calculator, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling for specialized math. The "$x402 pago por llamada" tag hints at the payment precondition but does not explain when that matters.

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