Skip to main content
Glama

Co Stacja Neapol robi sama

whats_made_here
Read-only

Użyj, gdy ktoś pyta, czym Stacja Neapol się wyróżnia, czy warto tam pojechać albo co robią sami. Każde wywołanie oddaje jeden, kolejny szczegół z zaplecza. Use when someone asks what makes Stacja Neapol different, whether it is worth the trip, or what they make in-house. Each call returns one more detail.

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

Input Schema

NameRequiredDescriptionDefault
afterNoId poprzedniego szczegółu, żeby dostać następny. / Id of the previous detail to get the next one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world and non-idempotent behaviour. The description adds genuinely useful context beyond that: calls are progressive, returning a single successive detail rather than a full list. It does not say what happens after the last detail is reached or whether the sequence is stable, which is the main remaining behavioural gap for a cursor-style tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The trigger condition is front-loaded and each sentence is purposeful. However the entire text is given twice, Polish and English, which doubles length without adding information for any single reader, and the return behaviour is buried in the final short clause.

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 simple single-parameter, read-only tool the description covers the trigger and the one-at-a-time progression. It leaves out what a returned detail looks like and, critically, what the agent should do when the sequence runs out, and there is no output schema to fill that gap.

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?

The input schema fully documents the single optional 'after' parameter and enumerates all six accepted ids in both languages, so baseline is 3. The description only implies chaining ('each call returns one more detail') and never explains that the previous detail's id is passed as 'after' or what happens when it is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete subject (Stacja Neapol's in-house details) and says each call returns one more of them, which is more than a restatement of the name. However the resource is described only vaguely as 'szczegół z zaplecza' / 'one more detail', so an agent cannot predict what kind of content it will get. It does not explicitly contrast itself with the siblings get_there_by_train, is_open_on or plan_visit, which overlap with the 'is it worth the trip' trigger.

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?

It gives three explicit triggering questions (what makes the place different, whether it is worth going, what they make themselves), which is clear when-to-use guidance. It stops short of stating when not to use it or which sibling to prefer for logistics/opening questions, so the boundary with plan_visit and is_open_on is left implicit.

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