Retrieve a quick overview of a statistical table to check its title, time range, and variables before deciding whether to fetch full metadata.
Get basic information about a table (title, time range, variables).
Use this for a quick overview before fetching full metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Language - 'no' for Norwegian (default), 'en' for English. | no |
| table_id | Yes | The table ID (e.g. '07459', '11342'). |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It clearly indicates a read-only retrieval operation and specifies the kind of data returned (title, time range, variables). While it doesn't discuss errors, pagination, or permissions, none of those are implied threats for this simple overview function.
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 short sentences deliver the core purpose and usage guidance with no filler. The primary functionality is front-loaded, and the usage note earns its place by clarifying when to invoke this tool.
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?
The description sufficiently covers what the tool does and what it returns given its low complexity and fully documented parameters. It could be slightly richer about the response structure, but for a basic overview tool, the information provided is adequate.
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 description coverage is 100%, so the input schema fully documents both table_id and language. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 states a specific action ('Get') on a clear resource ('table') and enumerates the scope of information returned (title, time range, variables). It also distinguishes itself from the sibling fetch_metadata by framing this as a 'quick overview' before full metadata retrieval.
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 phrase 'Use this for a quick overview before fetching full metadata' gives clear, context-specific guidance on when this tool is appropriate. It doesn't explicitly name alternatives or list when-not-to-use conditions, but the intended workflow is apparent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.