Skip to main content
Glama
il-opendata-mcp

il-opendata-mcp

by Shtibel1

Describe a datastore resource

describe_resource

Retrieve field names, types, and total record count for a CKAN datastore resource. Use it to inspect a resource's schema before querying records.

Instructions

Return field names/types and the total record count for a CKAN datastore resource (datastore_search with limit 0). Fails with a clear error if the resource has no active datastore — use get_dataset to find resources where datastore_active is true.

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": {
      "resource_id": "<resource_id>"
    },
    "name": "describe_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
resource_idYesCKAN resource UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the load and does disclose the key behaviors: it is a metadata-style read, it uses limit 0 under the hood, and it fails with a clear error for non-datastore resources. It omits pagination/volume or cost characteristics, which are minor here given the limit-0 design.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the return value and followed by the failure condition and fallback. No filler or repetition.

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?

For a one-parameter read tool with no output schema, the description states what is returned, the implementation detail that explains the cheapness, and the failure mode with a remediation path. Nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter is fully documented as a CKAN resource UUID. The description adds no further constraints or format detail about resource_id, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Return') plus the exact payload ('field names/types and the total record count') for a named resource type, and even names the underlying call (datastore_search with limit 0), so it is distinguishable from siblings like search_records and get_dataset.

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

Usage Guidelines4/5

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

Gives a concrete precondition: it fails when the resource has no active datastore, and routes the agent to get_dataset to find resources where datastore_active is true. It does not explicitly contrast against search_records, so the alternative routing is partial rather than complete.

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