Skip to main content
Glama

Link Energy México — Catálogo Público

get_product_details

Obtiene ficha técnica pública completa, precio MXN con 16% IVA, disponibilidad nacional, clave SAT CFDI 4.0 y URL canónica.

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": {
      "producto_id": "<producto_id>"
    },
    "name": "get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
producto_idYesSKU / ID numérico o identificador del producto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose that the data is 'pública' (implying no auth needed) and that the price already includes 16% IVA, which prevents an agent from double-applying tax. It omits what happens for an unknown product ID, whether the call is cached/rate-limited, and whether availability reflects real-time stock, so coverage is partial.

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?

A single front-loaded sentence with the verb and resource first, followed by a tight enumeration of returned fields. No filler, no restatement of the tool name, and every listed element adds information an agent cannot get from the schema.

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?

For a one-parameter lookup with no output schema, the description usefully enumerates the return payload, which is the main gap the missing output schema leaves. However, it never names the input parameter or addresses error/empty-result behavior, so it is adequate rather than complete.

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% for the single 'producto_id' parameter, so the schema already defines it as SKU / numeric ID / product identifier. The description adds nothing about accepted ID formats or validation, so the baseline of 3 applies when the schema does all the work.

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?

States a specific verb ('Obtiene') and a concrete resource ('ficha técnica pública completa') and enumerates exactly which data points come back (price with VAT, availability, SAT code, canonical URL). An agent immediately understands the payload, but the description never differentiates this tool from siblings like search_products or compare_products, leaving the routing decision to the name alone.

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 explicit when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as the sibling search or compare tools. Usage must be inferred from the name and the fact that it takes a single product ID; nothing states when this tool is the wrong choice.

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