Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

City rankings

transita_rankings
Read-onlyIdempotent

Rank Transita's profiled cities on one dimension such as safety, healthcare or tech jobs, highest score first, optionally within one country. Scores run 0 to 100 and are editorial estimates built from the public sources the methodology names, not official statistics.

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": {
      "dimension": "<dimension>"
    },
    "name": "transita_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost cities to return, e.g. 10. Default 10.
countryNoLowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK.
dimensionYesRanking dimension slug, e.g. 'safety', 'healthcare' or 'tech-jobs'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds meaningful context beyond annotations by disclosing that the scores are 0–100 editorial estimates from named public sources, not official statistics.

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 carry the core behavior and the important data-quality caveat without wasted wording. The ranking semantics are front-loaded before the provenance note.

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 ranked-list tool with no output schema, the description gives the key return characteristics: highest score first and a 0–100 editorial score range. It does not describe the exact result fields, but that is a minor gap against the otherwise complete parameter and annotation context.

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 coverage is 100%, so the parameters are already well documented. The description reinforces the dimension and optional country semantics but adds little beyond the schema; the limit parameter is not discussed in the description.

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 states a specific verb and resource: ranking Transita's profiled cities on one dimension. It also clarifies scope (highest score first, optional country filter), which makes it easy to distinguish from the visa-focused sibling tools.

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 implied by 'Rank ... on one dimension ... optionally within one country,' but there is no explicit guidance on when to choose this over country or cost-of-living siblings. It gives enough context to understand the basic call but leaves alternative routing to inference.

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

All Transita toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources