Skip to main content
Glama
Sign In

SafeStreets

by io.github.Poseidon-t
OverviewDiscussionsAdmin

get_city_walkability

Read-onlyIdempotent

Walkability score for a whole US city, precomputed. Instant, no analysis.

Use this for "how walkable is Houston" rather than scoring a point inside it. Returns the 0-100 composite, the same score as 0-10, the tier, and the four components. Covers 203 cities; a city not in the set returns null, which means not covered rather than not walkable.

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": {
      "city": "<city>"
    },
    "name": "get_city_walkability"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name or slug, e.g. "Houston", "fort worth", "chicago".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior. The description adds valuable context beyond annotations: precomputed/instant, no analysis, return fields, coverage size, and the crucial null-means-not-covered semantics.

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?

Front-loads the core purpose, then gives usage differentiation, return details, and coverage/null semantics in compact form. Every sentence adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter precomputed lookup tool with no output schema, the description covers purpose, usage, return shape, coverage limits, and null behavior. Annotations cover the safety profile, so no important call-decision information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the city parameter is already well documented with name/slug examples. The description adds useful parameter-related meaning by stating coverage is limited to 203 cities and that an unlisted city returns null rather than indicating low walkability.

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 (walkability score for a whole US city) and scopes it as precomputed and instant. It also distinguishes city-level scoring from scoring a point inside a city, so an agent can separate it from point-level siblings.

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?

Gives an explicit use case ('how walkable is Houston') and an explicit alternative behavior to avoid ('scoring a point inside it'). The coverage note about 203 cities and null for uncovered cities further clarifies when this tool applies.

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

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