Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Szukaj zamawiających i wykonawców

search_entities
Read-onlyIdempotent

Find contracting authorities (kind='buyer', zamawiający) or contractors (kind='contractor', wykonawcy — companies and sole traders) by name or NIP. Returns each match with its city, voivodeship, slug and public URL; pass the slug to get_buyer / get_contractor. Requires OAuth authentication and a trial or paid plan.

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": {
      "kind": "<kind>",
      "query": "<query>"
    },
    "name": "search_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
limitNo
queryYesName fragment as written in Polish, or NIP, e.g. 'gmina wieliczka' or '6772...'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Name fragment or NIP, e.g. 'gmina wieliczka' or '6772...'"New value: +"Name fragment as written in Polish, or NIP, e.g. 'gmina wieliczka' or '6772...'"
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +20
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds what the structured fields do not: OAuth plus a trial or paid plan is required, and each match returns city, voivodeship, slug and public URL. Pagination/limit behavior is not explained.

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?

Three tightly packed sentences: purpose and kind semantics first, then return values and next step, then prerequisites. Every clause carries information, though the opening sentence is dense enough to slow parsing slightly.

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 no output schema, the description correctly supplies the return shape and the slug handoff to detail tools, and it discloses the auth/plan gate. The only real gap is result-count/pagination behavior via limit, which an agent might need for broad queries.

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?

Schema coverage is only 33% (only 'query' is documented in schema), so the description compensates by mapping kind to buyer vs contractor and explaining query accepts either a Polish name fragment or a NIP. The limit parameter (default 20, max 20) is left unmentioned in both places.

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 verb (find) plus both resource types, and defines the kind values inline with Polish domain terms ('zamawiający', 'wykonawcy — companies and sole traders'). This clearly separates it from get_buyer/get_contractor, which fetch one entity by slug rather than searching.

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 implies the intended flow: search here to obtain a slug, then pass it to get_buyer / get_contractor. It also names the two input modes (name fragment or NIP). It does not say when not to use it (e.g. for tender search, use search_tenders), so it stops short of full routing guidance.

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