Skip to main content
Glama
Sign In
ruter-connector

ruter-connector

by fredrsat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Finn stoppested

finn_stoppested

Search Norwegian public transport stops and stations by name to get the NSR IDs needed for departure lookups.

Instructions

Søk etter holdeplass/stasjon i Norge etter navn (f.eks. «Jernbanetorget» eller «Nydalen»). Returnerer NSR-id-er som brukes i avganger-verktøyet. Bruk alltid dette først hvis du ikke kjenner id-en.

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": {
      "navn": "<navn>"
    },
    "name": "finn_stoppested"
  }
}

Input Schema

NameRequiredDescriptionDefault
navnYesNavn på holdeplass eller stasjon, f.eks. «Majorstuen»
antallNoMaks antall treff

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the key downstream contract (returns NSR-ids consumed by avganger) but doesn't state pagination/limit behavior or exact return shape beyond ids. Good but not exhaustive.

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, front-loaded with the core action, examples, return contract, and usage rule. No waste.

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?

Complete for a simple 2-param lookup with full schema coverage; the description covers purpose, return semantics, and sequencing with the sibling. Lacks only explicit note on what happens with no matches.

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 100%, so baseline 3. The description gives example name values matching the 'navn' param, but adds nothing about 'antall' beyond what the schema already documents.

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+resource in Norwegian ('Søk etter holdeplass/stasjon i Norge etter navn') and gives concrete examples. Clearly distinguishes itself from the sibling 'avganger' by explaining it returns NSR-ids used by that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Bruk alltid dette først hvis du ikke kjenner id-en' (always use this first if you don't know the id), naming the exact condition and the downstream alternative. Full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools