Skip to main content
Glama
Sign In

StayingAsia

by com.stayingasia
OverviewDiscussionsAdmin

List long stay routes

list_routes
Read-onlyIdempotent

The long stay instruments for one country, or across all countries filtered by family: remote-work, retirement, investment, skilled, business, family.

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

Input Schema

NameRequiredDescriptionDefault
familyNoFilter by route family, for example "remote-work" or "retirement"
countryNoCountry name or slug, omit for every country

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds domain context about long stay instruments and family categories, but no additional operational traits such as rate limits or output behavior.

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

Conciseness4/5

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

A single dense sentence containing only relevant scope and filter information. The noun-phrase opening is slightly indirect, but there is no wasted wording.

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 read-only tool with two optional parameters, full schema coverage, and annotations, the description covers the core scope and filters adequately. It does not explain return structure or sibling routing, but neither is critical given the tool's simplicity.

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%, and both parameters are documented in the schema. The description reinforces that country can be omitted for all countries and lists family examples, but adds only marginal meaning beyond the schema.

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

Purpose4/5

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

States the resource as long stay instruments/routes and explains the two scoping modes: one country or all countries filtered by family. The purpose is clear, though it does not explicitly distinguish itself from siblings such as country_overview or find_guides.

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?

The description implies when to use the tool for long stay route retrieval and clarifies country-vs-all-country filtering. It does not provide explicit when-not guidance or name alternative tools, leaving sibling selection to inference.

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

All StayingAsia 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