Skip to main content
Glama

Consultar precios

consultar_precios
Read-onlyIdempotent

Devuelve los precios actuales de cvwork: crear el CV es gratis, pase Premium de 30 días y plantilla premium suelta. Úsala cuando pregunten cuánto cuesta hacer un CV, si es gratis o qué incluye Premium.

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine value by disclosing what the response contains (the three price categories), which matters since there is no output schema. It says nothing about currency, price volatility, or freshness beyond "actuales", leaving some behavioral gaps.

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?

Two sentences, front-loaded with the returned content followed by the usage triggers; every clause carries information and there is no filler or redundancy.

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 zero-parameter, read-only lookup with no output schema, the description covers both what is returned and when to call it. The remaining gap is the shape of the return (currency, formatting, whether prices are locale-specific), which cannot be inferred from any structured field.

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 there is no parameter meaning to add and the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

"Devuelve los precios actuales de cvwork" gives a specific verb (devuelve) and resource (precios), then enumerates the three price items covered: free CV creation, 30-day Premium pass, and standalone premium template. It is unambiguous what the tool answers, though it never explicitly contrasts itself with siblings like listar_plantillas, which also touches on templates.

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

Usage Guidelines4/5

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

The second sentence gives concrete activation triggers: when the user asks how much making a CV costs, whether it is free, or what Premium includes. That is clear when-to-use guidance. It stops short of exclusions or naming an alternative tool for adjacent questions (e.g. template listings), so it falls short of a 5.

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