Skip to main content
Glama

PS Group: wykrywanie wycieków i osuszanie

Usługi PS Group

lista_uslug
Read-only

Usługi PS Group: wykrywanie wycieków wody, osuszanie po zalaniu, serwis i monitoring dachów płaskich, usuwanie grzybów i pleśni. Z opisem i adresem strony.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, closed-world operation, so the safety profile is covered. The description adds useful behavioral context by stating that returned entries include a description and a website address, which tells the agent what payload to expect beyond the annotation hints.

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 short and front-loaded with the service categories, with no filler. The opening phrase 'Usługi PS Group:' largely repeats the title, and the final fragment 'Z opisem i adresem strony' is terse, but the overall structure is efficient.

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?

For a simple, parameterless, read-only listing tool without an output schema, the description gives enough context: it identifies the domain (PS Group services), the categories covered, and the additional fields returned. It could be more explicit that the result is a list, but no critical information is missing for correct invocation.

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?

The tool takes no parameters, so there is nothing for the description to clarify beyond what the empty schema already shows. The baseline for zero parameters 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 enumerates the specific service categories (water leak detection, drying after flooding, flat roof servicing, mold/fungus removal) and notes that each comes with a description and website address. It does not explicitly say 'lists' and does not differentiate from siblings like kontakt or szukaj, but the resource is clear.

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 content: an agent can infer this tool is for browsing PS Group's service offerings. There is no explicit when-to-use guidance, no exclusion criteria, and no comparison with alternatives such as szukaj.

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