Skip to main content
Glama

PS Group: wykrywanie wycieków i osuszanie

Szukaj na psgroup.pl

szukaj
Read-only

Wyszukuje podstrony i poradniki psgroup.pl po frazie (np. osuszanie podposadzkowe, wyciek Kraków). Zwraca do 5 wyników z tytułem, adresem i fragmentem.

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": {
      "fraza": "<fraza>"
    },
    "name": "szukaj"
  }
}

Input Schema

NameRequiredDescriptionDefault
frazaYesSzukana fraza, np. osuszanie po zalaniu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: a hard cap of 5 results and the shape of each result (title, address, snippet), which compensates for the absent 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.

Conciseness5/5

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

Two compact sentences: the first front-loads the action and scope, the second states the return shape. Every clause carries information and nothing is padded.

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

Completeness5/5

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

For a single-parameter read-only search tool, the definition covers what it searches, the query form, the result count limit and result fields. With annotations covering safety and no output schema to explain, nothing essential is missing.

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?

With one parameter and 100% schema description coverage, the schema already documents "fraza" including its own example. The description's phrase examples add a little insight into query style (service + location) but do not add constraints or semantics beyond the schema, so the 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?

The description names a specific verb ("Wyszukuje") and a precise resource scope (psgroup.pl subpages and guides), plus a result cap of 5 with title/URL/snippet. It does not explicitly distinguish itself from the sibling tools kontakt or lista_uslug, so it stops short of a 5.

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 only implied by the sample queries ("osuszanie podposadzkowe, wyciek Kraków"), which hint at a keyword/site-search use case. There is no explicit statement of when to prefer this over kontakt or lista_uslug, and no exclusions.

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