Skip to main content
Glama

Honorarios de MisCausas

consultar_precios
Read-onlyIdempotent

Honorarios publicados por MisCausas.cl para cada servicio (en UF o en pesos), cómo se convierte la UF y las condiciones: gastos de terceros, pago en cuotas, acompañamiento posterior.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consultar_precios"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that results include UF/peso amounts, the UF conversion, third-party expenses, installment payment and follow-up support, which usefully describes what comes back given there is no output schema. It does not say whether prices are static or how stale they may be.

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 identifies the source and price basis (UF or pesos) before listing the supporting details. The trailing colon-list of conditions is dense but every item carries information; nothing is repeated from structured fields.

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?

With no parameters and no output schema, the description has to carry the entire burden of describing what is returned, and it does cover currency, UF conversion and the payment conditions. Minor gaps remain, such as whether fees are tax-inclusive or how current the published prices are, but nothing needed to invoke it is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the schema leaves nothing to interpret and the baseline of 4 applies. The description correctly presents this as a self-contained lookup with no inputs to supply.

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 names a specific resource (published MisCausas.cl fees per service) and the content it covers, so an agent can tell it is a pricing lookup rather than a generic service listing. It never explicitly contrasts itself with siblings such as listar_servicios, so differentiation is left to inference.

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?

Use is only implied: an agent can guess this is the tool for cost/fee questions because the content is pricing, UF conversion and payment conditions. There is no explicit when-to-use statement, no mention of when to prefer listar_servicios, and no exclusions.

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