Skip to main content
Glama

FinPortal.mk Financial Intelligence

Линии на ЈСП

get_jsp_routes
Read-onlyIdempotent

Fetch the public Skopje bus routes from skopjebus.mk, grouped as city, regional, and night routes. Use the returned internal route ID with get_jsp_schedule; the line number is a separate display label.

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

Input Schema

NameRequiredDescriptionDefault
groupNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond them by naming the upstream data source and by warning that the internal route ID differs from the display line number, which prevents a common misuse. Return shape and pagination remain undisclosed, keeping it out of the top band.

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 sentences with zero filler. The scope statement comes first and the critical ID-versus-line-number caveat is front-loaded before any invocation attempt.

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 single-parameter, read-only list tool with no output schema and rich annotations, the description covers source, grouping, and the key ID semantics. It could still say what a route entry contains or whether the group value filters server-side, but nothing essential to calling it correctly 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?

Schema description coverage is 0%, so the description must carry the parameter burden. It loosely maps the grouping to 'city, regional, and night routes' in prose, but never names the `group` parameter, never mentions that 'all' is the default, and uses 'city' where the enum value is 'Urban', leaving a capitalization mismatch for the agent to reconcile.

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?

The description names a specific verb and resource (fetch public Skopje bus routes from skopjebus.mk) and states the organizing structure (city, regional, night). It also distinguishes itself from the sibling get_jsp_schedule by clarifying that this tool returns the route catalog whose IDs feed the schedule tool.

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 a clear chaining instruction: use the returned internal route ID with get_jsp_schedule. That tells the agent when this tool is the right first step. It stops short of explicit when-not guidance or naming any other alternative.

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