InfoGrunt

Szczegóły jednego tematu działki

get_parcel_section

Read-onlyIdempotent

Szczegóły jednego tematu dla działki, np. plan miejscowy, powódź, media, dojazd albo ceny transakcji w okolicy. Ze źródłem, datą i linkiem do strony działki.

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": {
      "parcel_id": "<parcel_id>",
      "section": "<section>"
    },
    "name": "get_parcel_section"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Temat: mpzp = plan miejscowy, wz = warunki zabudowy, flood = powódź, utilities = media, road_context = dojazd, transactions = ceny w okolicy.
`parcel_id`	Yes	Pełny numer ewidencyjny działki (z find_parcel albo find_parcel_at_point), np. 101710_2.0007.1504/6.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 13, 2026

addedInput schema / properties / parcel_id / description

Added value: +"Pełny numer ewidencyjny działki (z find_parcel albo find_parcel_at_point), np. 101710_2.0007.1504/6."

addedInput schema / properties / parcel_id / examples
```
Added value: +[
+  "101710_2.0007.1504/6"
+]
```

addedInput schema / properties / section / description

Added value: +"Temat: mpzp = plan miejscowy, wz = warunki zabudowy, flood = powódź, utilities = media, road_context = dojazd, transactions = ceny w okolicy."

addedInput schema / properties / section / examples
```
Added value: +[
+  "mpzp"
+]
```

First observedOct 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered without prose. The description adds some value by stating the response carries a source, date and link to the parcel page, but says nothing about latency, rate limits or what happens for a section with no data.

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?

A single short sentence with the examples front-loaded and zero padding. It is efficient, though the examples overlap with what the schema already lists.

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 fully-specified required parameters, 100% schema coverage, and an output schema that handles return values, the description covers what is needed to call the tool correctly. Only the relationship to sibling tools is left implicit.

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 section enum is fully documented in the schema, so the baseline is 3. The description's topic examples (mpzp, flood, utilities, road context, transactions) echo the enum values and add only mild gloss, not meaning beyond the schema.

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 a specific verb and resource (details of a single section/topic for a parcel) and enumerates concrete topic examples (local plan, flood, utilities, access road, transaction prices), which lets an agent distinguish it from a broad overview tool. The one-topic scope is clear, though it never names the sibling it complements (get_parcel_overview).

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?

Usage is implied by the 'one topic per call' framing and the topic examples, so an agent can infer that it should be called once per section of interest. There is no explicit when-to-use/when-not guidance and no named alternative for obtaining all topics at once or for obtaining the parcel_id, leaving routing to inference.

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

All InfoGrunt 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?