Skip to main content
Glama
Sign In

SafeStreets

by io.github.Poseidon-t
OverviewDiscussionsAdmin

search_insights

Read-onlyIdempotent

Search SafeStreets' published research on walkability, street design and pedestrian safety.

Returns the article title, summary, URL and its published questions and answers, so a finding can be quoted and linked rather than paraphrased from memory. 32 articles, each built on named public sources.

Use this when someone asks what the evidence says, wants a figure they can cite, or asks a general question about walkability that is not about one specific location.

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": {
      "query": "<query>"
    },
    "name": "search_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many articles, default 5.
queryYesWhat to look for, e.g. "car free cities", "arterial roads", "kids walking to school".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description's added value is the return payload (title, summary, URL, published Q&A) and the rationale for using it (quote and link rather than paraphrase). It doesn't mention ranking/relevance behavior or what happens when no article matches, which keeps it below a 5.

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 paragraphs: purpose, what comes back, when to use. Front-loaded with the scope statement and no filler; every sentence carries distinct information.

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?

With no output schema, the description compensates by enumerating return fields, and it also supplies corpus size and source provenance, which an agent needs to decide whether the tool is authoritative enough to cite. Nothing essential for correct invocation is missing.

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% and both parameters carry their own descriptions, including examples for query and the default/max for limit, so the schema does the heavy lifting. The description adds no syntax, matching, or phrasing guidance beyond what the schema already states — the baseline 3 applies.

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?

Specific verb (search) plus a precisely scoped resource (SafeStreets' published research on walkability, street design, pedestrian safety), with corpus size (32 articles) and provenance (named public sources) stated. It is clearly separable from the sibling tools, which are all location-scoped scoring/lookup tools.

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 three explicit trigger conditions (what the evidence says, a citable figure, a general question) and an explicit exclusion: 'not about one specific location,' which routes location-specific queries to siblings like get_city_walkability or find_walkable_neighborhoods. Both when and when-not are covered.

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