Skip to main content
Glama

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

recommend_cctv_kit

Dimensiona almacenamiento CCTV en Terabytes (H.265+), canales de grabador NVR y discos duros WD Purple / Seagate SkyHawk 24/7 junto con SKUs reales disponibles en México.

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": {
      "cameras_count": "<cameras_count>"
    },
    "name": "recommend_cctv_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
environmentNoAmbiente de instalaciónoutdoor
cameras_countYesNúmero de cámaras requeridas
resolution_mpNoResolución objetivo en Megapíxeles (2MP, 4MP, 5MP u 8MP/4K)
retention_daysNoDías continuos de grabación requeridos
brand_preferenceNoMarca preferida opcional (ej. HIKVISION, HILOOK, EPCOM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by disclosing the output composition (SKUs available in Mexico) and the assumptions baked into the sizing (H.265+ compression, 24/7-rated Purple/SkyHawk drives, NVR channel count), but says nothing about whether it is read-only, whether recommendations are deterministic, or whether pricing/currency is included.

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 dense sentence with the core verb front-loaded and zero filler. It is somewhat comma-heavy and packs three deliverables plus a locality constraint, but every clause contributes information.

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 five parameters, full schema coverage, no annotations, and no output schema, the description supplies what's missing: the computed outputs and the market/locality constraint. It stops short of stating whether cameras themselves are included or what the response shape looks like, which is the main remaining gap.

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%, so every parameter including enums and defaults is already documented. The description adds only indirect meaning (that camera count, retention, and resolution feed the TB/channel calculation) without clarifying units, defaults, or how brand preference alters results, so baseline 3 applies.

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 and resource set: sizes ('Dimensiona') CCTV storage in TB under H.265+, NVR channels, and 24/7 surveillance drives, returning real SKUs available in Mexico. An agent can tell this is a sizing/recommendation tool rather than a catalog lookup, though it never names a sibling to contrast with.

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?

No explicit when-to-use, when-not-to-use, or alternative routing. The domain (CCTV kit sizing from camera count/retention/resolution) makes the intent inferable, but nothing tells the agent when to prefer this over searching products or comparing kits, and no prerequisites are stated.

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