Skip to main content
Glama

enumerate_wbgapi_indicators

Idempotent

Enumerates all WDI indicators into columns, concepts, and bindings, enabling agents to map indicator concepts to physical data fields without duplicating bindings.

Instructions

Enumerate all WDI indicators into columns + concepts + bindings (idempotent).

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

Input Schema

NameRequiredDescriptionDefault
databaseNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered before the description is read. The description adds that results are materialized into columns, concepts and bindings, which reveals what gets written, but its '(idempotent)' marker simply repeats the annotation. It says nothing about volume, runtime, or remote-API dependency implications of enumerating 'all' indicators.

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 short sentence with the operation and its outputs front-loaded and no filler. The parenthetical is compact, though '+ concepts + bindings' reads as terse shorthand rather than explanatory prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotation set covers safety and idempotency. The description states the sweep scope ('all WDI indicators') and the artifacts produced, which is the essential information for this operation alongside the structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter ('database') with 0% schema description coverage and no default explanation in the schema, so the description must compensate. It never mentions the parameter at all, leaving the agent unable to tell whether omitting it enumerates into the default database or whether a named target is required.

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 concrete verb ('Enumerate') and resource ('WDI indicators') and states where the results land ('columns + concepts + bindings'), so the agent can tell this is a catalog-population operation rather than a query. It does not name or distinguish itself from any sibling tool, and 'WDI' and 'columns' are left as unexplained jargon.

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 when-to-use guidance, no prerequisite information, and no pointer to an alternative such as a listing or import tool. The only usage-adjacent signal, '(idempotent)', is about safe re-execution rather than about when this tool is the correct choice.

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