Skip to main content
Glama
Sign In
ezd-puw-mcp

ezd-puw-mcp

by gacabartosz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ezd_koszulka_search

Read-only

Find koszulki (document covers) in EZD PUW by barcode, year, RPW number, document ID, or other criteria.

Instructions

Wyszukaj koszulki w systemie EZD PUW po roznych kryteriach.

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": "ezd_koszulka_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
CIDNoCorrelation ID — identyfikator procesowości (auto-generated if omitted)
RocznikNoRocznik koszulki
NumerRpwNoNumer RPW (Rejestr Przesylek Wplywajacych)
kodkreskowyNoKod kreskowy koszulki
IdDokumentuPismaNoIdentyfikator dokumentu pisma
IdPracownikaWlascicielaNoID pracownika właściciela (defaults to EZD_WORKER_ID env)
IdStanowiskaWlascicielaNoID stanowiska właściciela (defaults to EZD_POSITION_ID env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations provide readOnlyHint: true, but the description adds no behavioral context beyond the basic search action. It does not explain matching semantics, pagination, result size, handling of omitted parameters, or any other runtime behavior, so an agent cannot anticipate what the tool will do in edge cases.

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?

The description is one short, front-loaded sentence with no filler or redundant wording. It is concise and easy to parse, though it sacrifices useful behavioral detail for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with seven optional parameters, no required parameters, no output schema, and no usage guidance, this description is too sparse. An agent cannot determine what an empty call returns, how criteria combine, or when this tool is preferable to related koszulka tools.

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 seven parameters are documented in the input schema. The description only adds the generic phrase 'po roznych kryteriach' and does not enrich parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the action ('Wyszukaj' / search) and the resource ('koszulki'), and mentions that searches can be done by various criteria. It does not explicitly distinguish itself from siblings like ezd_koszulka_list or ezd_koszulka_get, though the name and wording imply a filtered lookup.

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 guidance on when to use this tool versus alternatives such as ezd_koszulka_list, ezd_koszulka_get, or ezd_koszulka_list_documents. 'Po roznych kryteriach' weakly implies filtered search, but no selection conditions, exclusions, or alternative routing are provided.

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

Deploy Server

Other Tools