street-generator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_streetA | Render a StreetConfig as an illustrated SVG cross-section (people, cars, trees included). Claude produces the StreetConfig from the user's description; this tool draws it deterministically in the Street Generator visual style. |
| build_share_urlA | Return a streetgenerator.com link that opens this StreetConfig in the live Street Generator app. |
| import_street_from_osmA | Render a real street cross-section by reading its layout from OpenStreetMap. Requires a COMPLETE address: street, house number, city, postcode, and country. If the user hasn't provided all of these, or the address is unclear, ASK them for the missing parts before calling. If several places match, the tool returns lettered candidates (A, B, C…); show them to the user, then call again with the chosen candidate's lat and lng. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a unique purpose: build_share_url creates a sharing link, import_street_from_osm fetches real-world data, and render_street visualizes a config. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with snake_case: build_share_url, import_street_from_osm, render_street.
With only 3 tools, the set is slightly minimal but covers the core workflow of import, render, and share for street generation. The count is reasonable for a focused domain.
The tools cover import, render, and share, but lack any editing or querying capabilities for generated configurations. The user must rely on Claude to produce the StreetConfig, which may be a gap for manual adjustments.