Skip to main content
Glama

dataset_info

Read-onlyIdempotent

Data dates, sources, listing counts per portal, method notes and caveats (zrodla, daty, ograniczenia danych).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds nothing behavioral beyond that — no note on cost, no guidance on how authoritative the caveats are, no indication of anything an agent could not get from the annotations. What it does list (returned content) overlaps with the existing output schema.

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

Conciseness3/5

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

It is a single line with no wasted preamble, which is good, but it is a bare fragment that is not front-loaded with a purpose statement. The parenthetical Polish translations (zrodla, daty, ograniczenia danych) duplicate the English terms without adding meaning for most callers.

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?

With no parameters, rich annotations, and an output schema, the definition is not required to explain return values or safety. Still, for a metadata/caveats tool the description should convey why and when an agent must consult the caveats; that framing is absent, leaving the definition minimally adequate rather than complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description does not need to explain arguments and correctly avoids doing so.

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

Purpose3/5

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

The description enumerates the contents (dates, sources, listing counts, method notes, caveats) but never states a verb or explicitly says this returns dataset metadata. An agent can infer the resource from the name plus this list, yet the phrasing is a noun fragment rather than a clear statement of what the tool does. It is distinguishable from the rent/neighborhood siblings only by implication.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no reference to any sibling tool. The agent is left to guess whether this should be called before interpreting rent_stats or reachable_neighborhoods results. Only implicit usage (consult for caveats) can be read into the text.

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.

Resources