Skip to main content
Glama

Indice Local Estado

indice_local_estado
Read-onlyIdempotent

Count local index documents by type to confirm available jurisprudence volumes before querying.

Instructions

Cantidad de documentos del índice local por tipo.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that the payload is per-type document counts, which is close to what the output schema already conveys. It says nothing about which index is 'local', how current the counts are, or whether the operation is cheap — the kind of context that would justify a higher score.

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 short sentence with no filler, and the key information (counts, by type) is front-loaded. It is arguably too terse rather than too long, but nothing in it is wasted.

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 an output schema present and no inputs, the description does not need to explain return values, and it does state the core measure. However, it leaves 'índice local' and the set of possible 'tipos' undefined, and gives no hint of when an agent should reach for this versus the search tools. Adequate but with clear gaps for a tool whose whole value is orienting the agent.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no input is needed.

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 states a concrete resource and output: document counts from the local index, broken down by type. That is enough to tell it is a statistics/inventory tool rather than one of the search siblings, although it never names a sibling or explicitly contrasts itself with the buscar tools. The only friction is that the tool name/title say 'estado' (status) while the description describes counts, which is a small mismatch an agent must reconcile.

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 statement, no when-not-to-use, and no reference to alternatives. The agent must infer that this is a diagnostic/overview call to be made before or instead of the search tools. No prerequisites, no indication of cost or freshness are given.

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