Skip to main content
Glama

Smlouvy obce z Registru smluv

smlouvy_obce
Read-onlyIdempotent

Najde smlouvy obce v Registru smluv (s kým, kdy a za kolik obec smlouvu uzavřela). Obec zadejte IČO nebo jednoznačným názvem.

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": {
      "obec": "<obec>"
    },
    "name": "smlouvy_obce"
  }
}

Input Schema

NameRequiredDescriptionDefault
obecYesIČO obce (8 číslic) nebo jednoznačný název.
od_dataNoVolitelně nejdřívější datum podpisu, RRRR-MM-DD.
klicova_slovaNoVolitelně protistrana nebo předmět smlouvy, nejvýše 5 slov.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the data source (Registr smluv) and the nature of the returned content, but says nothing about result volume, pagination, or date/keyword scoping behavior.

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 tight sentences, front-loaded with the purpose before the input directive, with no filler. Slight redundancy between the second sentence and the schema's obec description keeps it from a 5.

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?

For a read-only, 3-parameter search tool with 100% schema coverage and annotations carrying the safety profile, the description is adequate. It is missing result-limit/pagination expectations and any routing to sibling tools, which leaves gaps for an agent deciding how to use it.

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 all three parameters are already documented in the schema. The description only reiterates the obec input format, adding no semantics beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource: 'Najde smlouvy obce v Registru smluv' and even previews the returned fields ('s kým, kdy a za kolik'). It is clear what the tool does, but it does not reference the potentially confusable sibling najit_obec (finding a municipality) to draw the boundary.

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?

No when-to-use or when-not guidance is given; it never says how it relates to siblings like hledat or najit_obec. The only instruction ('Obec zadejte IČO nebo jednoznačným názvem') is about parameter formatting, not about selecting this tool over alternatives.

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