SiteCheck Company Records

German open government datasets from GovData.de: title

gov_govdata_germany

Read-only

German open government datasets from GovData.de (CKAN API): title, publisher, licence, last modified date, number of resources and dataset link, for a search term. Catalogue metadata only, not the data files. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "gov_govdata_germany"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search text (German or English), 2 to 80 characters
`rows`	No	Datasets to return, 1 to 10 (default 5)

Output Schema

Name	Required	Description	Default
`query`	No
`source`	No
`datasets`	No
`checkedAt`	No
`totalDatasets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the data source API (CKAN) and materially important commercial behaviour: a $0.002 USDC charge per successful call via x402 on Base, Solana or Arc, with failed calls free. That payment condition is exactly the kind of behaviour an agent must know before invoking, and it is stated plainly.

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, front-loaded with the resource and scope, and the cost notice is isolated in its own sentence rather than buried. The first sentence is a field-list run-on, but every element (fields, scope exclusion, price, free-on-failure) carries information.

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?

With a 2-parameter schema and an output schema present, the description needs only to establish source, scope, cost and lookups; it does all four. Nothing an agent needs in order to decide or call 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%, so both q (2-80 chars, German or English) and rows (1-10, default 5) are already fully documented. The description adds only "for a search term", contributing no syntax, format or semantic detail beyond the schema, which is the expected baseline.

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 resource (German open government datasets from GovData.de via CKAN) and enumerates the return fields (title, publisher, licence, last modified, resource count, dataset link). The country/source qualifier separates it from the many sibling open-data tools such as gov_data_gov, gov_data_gov_uk and gov_australia_data_gov_au without needing to name them.

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?

"for a search term" plus the explicit exclusion "Catalogue metadata only, not the data files" tells an agent both the trigger and one clear non-use case. It stops short of naming an alternative tool (e.g. a file-download or other national catalogue) when the user actually wants the underlying data, so it falls short of full when/when-not/alternatives guidance.

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

All SiteCheck Company Records tools Inspect

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

Need Help?