Skip to main content
Glama
Sign In

SafeStreets

by io.github.Poseidon-t
OverviewDiscussionsAdmin

score_many

Read-onlyIdempotent

Score up to 10 US locations in one request.

Use this for a list: properties, branches, listings, sites.

Each location counts as one call against your allowance, so a list of ten costs ten. A location that cannot be resolved is reported in errors rather than failing the request.

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": {
      "locations": "<locations>"
    },
    "name": "score_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationsYesThe places to score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare safety/idempotency; the description adds two non-obvious behavioral facts the agent could not get elsewhere: a per-location quota cost ('a list of ten costs ten') and partial-failure semantics ('a location that cannot be resolved is reported in errors rather than failing the request'). That is exactly the kind of cost model and error-resilience disclosure annotations cannot carry.

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 short sentences, front-loaded with the capability and cap, then usage, then cost/error behavior. The synonym list ('properties, branches, listings, sites') earns its space by broadening recognition, and nothing is repeated.

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?

With no output schema, the description covers cost, limits, and the error channel well, but never says what a successful result contains (presumably a score per location, matched via the echoed label). The failure path is described while the success shape is left implicit.

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 nested fields already document label echoing and the address-or-lat/lon choice, so baseline is 3. The description adds the US-only geographic constraint and reinforces the 10-item ceiling, giving one genuine semantic addition 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 a specific verb and resource with a hard scope: 'Score up to 10 US locations in one request.' The batching limit and US restriction implicitly separate it from the single-location sibling get_walkability_score, but it never names that sibling explicitly.

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

Usage Guidelines4/5

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

'Use this for a list: properties, branches, listings, sites' gives a clear usage context with concrete examples. It stops short of an explicit exclusion (e.g., 'for a single point use get_walkability_score'), so the routing decision still requires the agent to infer from siblings.

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