Skip to main content
Glama

estado

Check database health before querying CNMC logistics data: reports the latest portal snapshot, data volume, incidents, and available tables.

Instructions

Estado de la base: última foto del portal, volumen de datos, incidencias y tablas.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the tool reports on portal snapshot recency, data volume and incidents — useful signals that this is an informational/diagnostic read. It does not state whether it triggers a live portal fetch, whether it is cheap or slow, or how to interpret staleness. Adequate but not rich.

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 front-loaded sentence with the subject ("Estado de la base") first and the content areas following. The trailing list is telegraphic rather than prose, but no words are wasted and nothing is buried.

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?

A parameterless diagnostic tool with an output schema, so return values need no explanation in the description. The content categories give enough orientation for an agent to call it correctly. It would be stronger with a note on when the snapshot is considered stale or what incidents imply.

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; the baseline for a parameterless tool is 4. The description correctly implies no input is required by framing it as a plain status report.

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?

"Estado de la base" names the resource and the operation (reporting status) and enumerates the four content areas it covers: portal snapshot, data volume, incidents and tables. This is clearly distinct from siblings such as buscar_precios, consulta_sql or listar_operadores, which operate on specific data rather than overall database health. It stops short of a full verb phrase, but an agent can tell what it returns.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use statement, and no alternative is named. Usage is only implied by the content list: an agent would infer this is for checking data freshness, volume and incidents, e.g. before trusting results from other tools. Nothing excludes or routes away from siblings such as capacidades.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.