Skip to main content
Glama

TechStore México — Catálogo Público

get_buying_guide

Devuelve una guía verificada de ingeniería, tablas comparativas y FAQ oficiales de TechStore 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. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and it does little beyond the name. Saying the content is "verificada" and "oficial" implies authority but not behavior: nothing about read-only nature, permissions, rate limits, or what happens with an unrecognized topic. The default behavior when no topic is supplied (the parameter is optional) is never explained.

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 zero filler that enumerates the three things returned. Nothing could be removed without losing information.

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?

With one optional parameter and no output schema, the description should explain the no-topic default and roughly what shape the answer takes. It hints at content types but leaves the fallback behavior and output structure undefined, which matters for a documentation-fetch tool.

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% — the single optional topic parameter is documented with its full value list — so the schema does the heavy lifting. The description adds no meaning beyond the schema, but per the baseline rule this is an adequate 3.

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 gives a specific verb ("Devuelve") plus concrete content types: ingeniería guides, comparison tables, and official FAQs from TechStore México. That distinguishes it from siblings like search_products or compare_products, which operate on products rather than curated documentation. It stops short of naming which sibling handles related needs (e.g., product-level comparisons).

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 or when-not-to-use guidance, and no alternatives are mentioned. A reader can infer it is for pulling editorial/FAQ content rather than live product data, but that inference is never stated, and nothing says which requests belong to recommend_cctv_kit or compare_products instead.

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