Skip to main content
Glama

Wyznacz trasę szlakami

wyznacz_trase
Read-onlyIdempotent

Liczy dowolną trasę po znakowanych szlakach przez podane punkty (router aplikacji Tatry Planer): km, przewyższenie, czas tam, powrotu i całości, przebieg z czasem narastająco, link do planera. Użyj dla połączeń spoza katalogu („z Kuźnic przez Zawrat na Kozi Wierch”). Nazwy polskie albo słowackie.

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": {
      "punkty": "<punkty>"
    },
    "name": "wyznacz_trase"
  }
}

Input Schema

NameRequiredDescriptionDefault
punktyYesStart, punkty pośrednie po kolei i cel, np. ["Kuźnice", "Zawrat", "Kozi Wierch"].
z_powrotemNoPolicz też powrót tą samą drogą.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 the safety profile is covered; the description adds real value beyond that by listing the computed outputs and their structure (breakdown of outbound/return/total time, cumulative-time track, planner link). It also discloses a naming constraint (Polish or Slovak names), though it says nothing about failure behaviour for unrecognized place names.

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?

Three tight sentences: the core action and return payload first, then the usage rule, then the naming caveat. The output enumeration is dense but every item is distinct information an agent can use; nothing is redundant with the schema or title.

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?

No output schema exists, yet the description compensates by enumerating the returned fields. Together with the usage rule, the example, the language constraint and the schema's 2–8 point bounds, an agent has everything needed to invoke the tool correctly.

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?

With 100% schema coverage the baseline is 3, and the description goes beyond the schema by noting that point names may be Polish or Slovak — information the schema does not contain and that directly affects how the `punkty` array must be filled. It adds nothing for `z_powrotem`, but that parameter is already self-documenting with a default.

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 and resource: computes an arbitrary route along marked trails through the given points, and enumerates what it returns (km, elevation gain, outbound/return/total times, cumulative-time track, planner link). The phrase „połączeń spoza katalogu” implicitly sets it apart from the catalog-based sibling szukaj_tras, so an agent can choose between them without opening either schema.

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?

Explicitly says when to use it — for connections outside the catalog — and gives a concrete example („z Kuźnic przez Zawrat na Kozi Wierch”), which is exactly the selection cue an agent needs. It stops short of naming szukaj_tras as the alternative for catalogued routes, so the exclusion is implied rather than stated.

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