Skip to main content
Glama

Describe a source or operation

ireland_describe
Read-onlyIdempotent

With source only: the full dataset card (topics, geography levels, time coverage, cadence, dimensions, join keys, freshness, licence, auth, example questions). With operation too: its argument JSON schema, an example and its card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "ireland_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource id, e.g. 'cso'.
operationNoOperation, e.g. 'cso_get_data'. Omit for the source's card.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / operation / description
      Previous value: -"Operation, e.g. 'cso_get_data'."New value: +"Operation, e.g. 'cso_get_data'. Omit for the source's card."
    • changedInput schema / required
      Previous value: -[
      -  "source",
      -  "operation"
      -]New value: +[
      +  "source"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description earns credit by enumerating what the card actually contains (topics, geography levels, time coverage, cadence, dimensions, join keys, freshness, licence, auth, example questions), which tells the agent what it will learn before calling ireland_call. Error behavior for unknown source/operation ids is not addressed.

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?

Two sentences, both front-loaded with the mode distinction, and the long field list is dense but each item is informative about return content. It avoids preamble entirely; only minor cost is that the parenthetical enumeration is long, though it earns its space.

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

Completeness4/5

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

With only two parameters, full schema coverage, and an output schema, this description covers what an agent needs to select the tool and pick a mode. The main residual gap is routing against sibling discovery tools, which the description never addresses.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds genuine semantics beyond the schema: the presence or absence of 'operation' switches the tool from card mode to schema+example mode. That is the key behavioral meaning of the optional parameter and it is stated explicitly.

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 exactly what the tool yields in each of its two modes: a full dataset card when given only a source, or an operation's argument JSON schema plus example and card when given an operation. The resource (source or operation) and the split behavior are unambiguous. It does not, however, differentiate itself from siblings such as ireland_catalogue or ireland_about, which an agent must resolve on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly defines the two invocation modes ('with source only' vs 'with operation too'), which is real usage guidance within the tool. But it gives no guidance on when to prefer this over ireland_catalogue, ireland_about, or ireland_call, so the choice among siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.