series_in_tableList the data series contained in an INE table. Each series has a COD (series code, e.g. "IPC251852") and a Nombre describing the breakdown. Pass a COD to series_data.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Response language. Default EN. | |
| tableId | Yes | Numeric table Id, e.g. "50902". |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "tableId": "50902"
+ },
+ {
+ "lang": "ES",
+ "tableId": "50902"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false. Description adds context about return structure (COD and Nombre) but does not provide additional behavioral details beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, efficient, front-loaded with purpose. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple tool (2 params, no output schema, rich annotations), description adequately explains output structure and usage hints. Completes the picture for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear parameter descriptions. Description does not add new semantics beyond the schema; it implicitly reinforces tableId's role but doesn't elaborate on lang or provide examples.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it lists data series in an INE table, specifies attributes (COD and Nombre), and hints at downstream tool (series_data). Distinguishes from sibling tools like series_data and table_data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to use this tool to list series within a table and mentions passing a COD to series_data for data retrieval. Lacks explicit when-not-to-use or alternative comparisons, but provides clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.