table_infoMetadata for a table: title, unit, last updated, and the full list of variables with their codes and valid value ids. READ THIS BEFORE get_data to learn the exact variable codes (e.g. "OMRÅDE", "Tid") and value ids you must pass.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language: "en" (default) or "da". | |
| tableId | Yes | Table id, e.g. "FOLK1C". |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "tableId": "FOLK1C"
+ },
+ {
+ "lang": "da",
+ "tableId": "FOLK1C"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds value by explaining the output includes variable codes and value ids, and reinforces the read-only nature by saying 'metadata'. No contradictions.
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: the first defines the output, the second gives a key usage instruction. Extremely concise and front-loaded with important information.
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?
For a simple metadata tool with full schema coverage and rich annotations, the description covers the return content and usage context completely. No output schema is needed because the description explains what is returned.
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%, so baseline is 3. The description does not add significant detail beyond the schema's parameter descriptions; it only gives example values in 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?
The description clearly states the tool returns metadata (title, unit, last updated, variables list) and explicitly positions it as a prerequisite for get_data, distinguishing it from that sibling tool.
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?
The description explicitly tells the agent to use this tool before get_data to learn variable codes and value ids, providing clear context. It does not list when not to use it, but the guidance is sufficient.
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.