Skip to main content
Glama

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

get_buying_guide

Devuelve una guía verificada de ingeniería, tablas comparativas y FAQ oficiales de Link Energy México.

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": "get_buying_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTema o sección: faq, solar-solutions, cctv-solutions, network-solutions, robotics-solutions, radio-solutions, solar-inverter-guide, solar-inverter-comparison, cctv-storage-guide, cedis-coverage-mexico

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Tema o sección: faq, solar-solutions, cctv-solutions, network-solutions, robotics-solutions, radio-solutions, solar-inverter-guide"New value: +"Tema o sección: faq, solar-solutions, cctv-solutions, network-solutions, robotics-solutions, radio-solutions, solar-inverter-guide, solar-inverter-comparison, cctv-storage-guide, cedis-coverage-mexico"
  2. First observed

TDQS

B3.2/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 behavioral burden itself. Calling the content 'verificada' and 'oficial' signals authoritative, presumably static, read-only reference data, which is useful context, but nothing is said about permissions, freshness, or what occurs if an unknown topic is passed.

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?

One front-loaded sentence with no filler, and the return contents (guide, comparison tables, FAQs) come before the vendor name. Nothing needs trimming.

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, read-only retrieval tool with no output schema, the description gives a rough sense of what comes back (engineering guide, comparison tables, FAQ). However, it never explains the default behavior when the optional topic is omitted, which is the main gap for calling it correctly.

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 100% and the single topic parameter already enumerates the valid sections, so the description cannot add much. It adds no meaning such as whether omitting topic returns all sections, leaving the optional-parameter behavior unstated.

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 uses a clear verb and resource ('Devuelve una guía verificada de ingeniería, tablas comparativas y FAQ oficiales') and names the source (Link Energy México), so an agent knows it fetches curated reference content. It does not explicitly differentiate from siblings like compare_products or search_products, which could overlap with 'tablas comparativas', so it stops short of 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 Guidelines2/5

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

There is no statement of when to use this tool, when not to, or which sibling to prefer for a given question. The agent must infer from the topic list that this is for static reference material rather than product search or kit calculation.

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