Skip to main content
Glama
Sign In

Data Lv

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query Resource

query_resource
Read-onlyIdempotent

Pull rows from a tabular Latvia Open Data resource (CKAN DataStore) by resource_id (from a dataset's resources). Optional full-text q, limit, offset. Note: only resources with the DataStore enabled are queryable.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource_id": "res-12345-abcde"
    },
    "name": "query_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional full-text filter over the rows.
limitNoMax rows (default 100).
offsetNoPagination offset.
resource_idYesA resource_id from dataset/search_datasets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "resource_id": "res-12345-abcde"
+  },
+  {
+    "limit": 50,
+    "q": "Riga",
+    "resource_id": "res-12345-abcde"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by specifying the data source (Latvia Open Data CKAN DataStore) and the queryability condition, enhancing the agent's understanding of behavior 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.

Conciseness5/5

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

The description is two sentences, front-loaded with the primary action and conditions. Every sentence provides essential information without redundancy.

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

Completeness3/5

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

While the input and condition are clear, the description does not hint at the output format (e.g., JSON rows). Given no output schema, the agent may need to infer the result structure. The annotations (readOnlyHint) partially cover safety, but completeness is adequate for a simple query tool.

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 coverage is 100%, with each parameter already described. The description reiterates these but adds minimal new context (e.g., 'from a dataset's resources' for resource_id). It does not significantly augment the schema's meaning.

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?

The description clearly states the tool pulls rows from a tabular CKAN DataStore resource by resource_id, with optional filters. This specific verb+resource pair distinguishes it from sibling tools like search_datasets which return datasets, not rows.

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?

The description notes that only resources with DataStore enabled are queryable, providing a clear precondition. While it doesn't explicitly contrast with alternatives, the sibling list includes search_datasets (for dataset lookup) and others, so context is implied.

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

All Data Lv toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources