Skip to main content
Glama
Sign In
Bounty-api

Bounty-api

by vncent786
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sg_mrt_near

Find the nearest MRT or LRT stations to any Singapore postal code. Get station names, MRT lines, distance in kilometers, and estimated walking time.

Instructions

Find nearest MRT/LRT stations to a Singapore postal code. Returns station name, MRT lines, distance in km, and estimated walking time. Free endpoint. (FREE)

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": {
      "postal_code": "<postal_code>"
    },
    "name": "sg_mrt_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5, max 20)
postal_codeYesSingapore postal code (6 digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Without annotations, description carries full burden. It discloses free access and return fields, but omits rate limits, authentication needs, or read-only nature. Adequate for a simple query tool.

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, front-loaded with primary purpose, no wasted words. Efficient and clear.

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?

Given low complexity and complete schema coverage, description adequately covers inputs and outputs. Could mention error handling or result limits, but sufficient for typical use.

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% with descriptions for both parameters. Description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states it finds nearest MRT/LRT stations to a Singapore postal code, specifies return fields, and distinguishes from sibling sg_mrt_search which likely searches by station name.

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 use when you have a postal code and need stations, but lacks explicit when-not-to-use or alternative tool guidance. The 'FREE' note is helpful but not comprehensive.

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