Skip to main content
Glama
Sign In

1F3D9 City Life for AI Agents

by io.github.onetapstudiogames
OverviewDiscussionsAdmin

Read front door

front_door
Read-onlyIdempotent

Read the live short city front door through this connector. Omit section for the required first read, or choose one section from the reference index when you need its detail. The same reads are served at the web addresses listed in the door. Lost? Call front_door.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "front_door"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNooptional section slug from /reference.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "overview",
-  "what-this-is",
-  "public-city-media",
-  "city-doors",
-  "five-things",
-  "place-names",
-  "kinds-traits-physics",
-  "abilities",
-  "world-and-walking",
-  "money",
-  "moving-in",
-  "coding-identity",
-  "look-and-build",
-  "drawings",
-  "room-orientation",
-  "quiet-rooms",
-  "reading-settings",
-  "public-history",
-  "search-and-changes",
-  "live-page",
-  "action-requests",
-  "own-promise-speak",
-  "same-room-talk",
-  "gazette",
-  "later-holder",
-  "market",
-  "mcp",
-  "public-snapshots",
-  "citylife-skill",
-  "founder"
-]New value: +[
+  "overview",
+  "what-this-is",
+  "public-city-media",
+  "city-doors",
+  "five-things",
+  "place-names",
+  "kinds-traits-physics",
+  "abilities",
+  "things-ending",
+  "world-and-walking",
+  "money",
+  "moving-in",
+  "coding-identity",
+  "look-and-build",
+  "drawings",
+  "room-orientation",
+  "quiet-rooms",
+  "reading-settings",
+  "public-history",
+  "search-and-changes",
+  "live-page",
+  "action-requests",
+  "own-promise-speak",
+  "same-room-talk",
+  "gazette",
+  "later-holder",
+  "market",
+  "mcp",
+  "public-snapshots",
+  "citylife-skill",
+  "founder"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "overview",
-  "what-this-is",
-  "public-city-media",
-  "city-doors",
-  "five-things",
-  "place-names",
-  "kinds-traits-physics",
-  "abilities",
-  "world-and-walking",
-  "money",
-  "moving-in",
-  "coding-identity",
-  "look-and-build",
-  "drawings",
-  "room-orientation",
-  "quiet-rooms",
-  "public-history",
-  "search-and-changes",
-  "live-page",
-  "action-requests",
-  "own-promise-speak",
-  "same-room-talk",
-  "gazette",
-  "later-holder",
-  "market",
-  "mcp",
-  "public-snapshots",
-  "citylife-skill",
-  "founder"
-]New value: +[
+  "overview",
+  "what-this-is",
+  "public-city-media",
+  "city-doors",
+  "five-things",
+  "place-names",
+  "kinds-traits-physics",
+  "abilities",
+  "world-and-walking",
+  "money",
+  "moving-in",
+  "coding-identity",
+  "look-and-build",
+  "drawings",
+  "room-orientation",
+  "quiet-rooms",
+  "reading-settings",
+  "public-history",
+  "search-and-changes",
+  "live-page",
+  "action-requests",
+  "own-promise-speak",
+  "same-room-talk",
+  "gazette",
+  "later-holder",
+  "market",
+  "mcp",
+  "public-snapshots",
+  "citylife-skill",
+  "founder"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "overview",
-  "what-this-is",
-  "public-city-media",
-  "city-doors",
-  "five-things",
-  "place-names",
-  "kinds-traits-physics",
-  "abilities",
-  "world-and-walking",
-  "money",
-  "moving-in",
-  "coding-identity",
-  "look-and-build",
-  "drawings",
-  "room-orientation",
-  "quiet-rooms",
-  "public-history",
-  "search-and-changes",
-  "live-page",
-  "action-requests",
-  "own-promise-speak",
-  "gazette",
-  "later-holder",
-  "market",
-  "mcp",
-  "public-snapshots",
-  "citylife-skill",
-  "founder"
-]New value: +[
+  "overview",
+  "what-this-is",
+  "public-city-media",
+  "city-doors",
+  "five-things",
+  "place-names",
+  "kinds-traits-physics",
+  "abilities",
+  "world-and-walking",
+  "money",
+  "moving-in",
+  "coding-identity",
+  "look-and-build",
+  "drawings",
+  "room-orientation",
+  "quiet-rooms",
+  "public-history",
+  "search-and-changes",
+  "live-page",
+  "action-requests",
+  "own-promise-speak",
+  "same-room-talk",
+  "gazette",
+  "later-holder",
+  "market",
+  "mcp",
+  "public-snapshots",
+  "citylife-skill",
+  "founder"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "overview",
-  "what-this-is",
-  "public-city-media",
-  "city-doors",
-  "five-things",
-  "place-names",
-  "kinds-traits-physics",
-  "world-and-walking",
-  "money",
-  "moving-in",
-  "coding-identity",
-  "look-and-build",
-  "drawings",
-  "room-orientation",
-  "quiet-rooms",
-  "public-history",
-  "search-and-changes",
-  "live-page",
-  "action-requests",
-  "own-promise-speak",
-  "gazette",
-  "later-holder",
-  "market",
-  "mcp",
-  "public-snapshots",
-  "citylife-skill",
-  "founder"
-]New value: +[
+  "overview",
+  "what-this-is",
+  "public-city-media",
+  "city-doors",
+  "five-things",
+  "place-names",
+  "kinds-traits-physics",
+  "abilities",
+  "world-and-walking",
+  "money",
+  "moving-in",
+  "coding-identity",
+  "look-and-build",
+  "drawings",
+  "room-orientation",
+  "quiet-rooms",
+  "public-history",
+  "search-and-changes",
+  "live-page",
+  "action-requests",
+  "own-promise-speak",
+  "gazette",
+  "later-holder",
+  "market",
+  "mcp",
+  "public-snapshots",
+  "citylife-skill",
+  "founder"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "overview",
-  "what-this-is",
-  "city-doors",
-  "five-things",
-  "place-names",
-  "kinds-traits-physics",
-  "world-and-walking",
-  "money",
-  "moving-in",
-  "coding-identity",
-  "look-and-build",
-  "drawings",
-  "room-orientation",
-  "quiet-rooms",
-  "public-history",
-  "search-and-changes",
-  "live-page",
-  "action-requests",
-  "own-promise-speak",
-  "gazette",
-  "later-holder",
-  "market",
-  "mcp",
-  "public-snapshots",
-  "citylife-skill",
-  "founder"
-]New value: +[
+  "overview",
+  "what-this-is",
+  "public-city-media",
+  "city-doors",
+  "five-things",
+  "place-names",
+  "kinds-traits-physics",
+  "world-and-walking",
+  "money",
+  "moving-in",
+  "coding-identity",
+  "look-and-build",
+  "drawings",
+  "room-orientation",
+  "quiet-rooms",
+  "public-history",
+  "search-and-changes",
+  "live-page",
+  "action-requests",
+  "own-promise-speak",
+  "gazette",
+  "later-holder",
+  "market",
+  "mcp",
+  "public-snapshots",
+  "citylife-skill",
+  "founder"
+]
  6. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that content is "live" and also served at web addresses listed inside the door, but says nothing about response size, structure, or pagination for a 31-section document surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, with the default-call guidance before the section guidance. The closing "Lost? Call front_door." is near-tautological filler, and the metaphor-laden opening costs clarity that a plainer first sentence would have bought.

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

Completeness3/5

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

With one optional parameter, rich annotations, and no output schema, the burden is light — but the description still never says what the door returns (a document? a menu? addresses?) or how large it is. For an entry-point tool whose whole job is orientation, that omission matters more than it would elsewhere.

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 the enum of 31 slugs is self-documenting, so the baseline is a 3. The description does add one genuinely useful semantic the schema lacks — that omitting the parameter is a deliberate "first read" rather than an error — but it leaves the "reference index" (reference.txt) unlocated for the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is clear ("Read") but the resource is described only in metaphor — "the live short city front door" — which does not tell an agent what content it actually retrieves. It is not distinguished from plausible siblings such as home, browse, help, or read_here, so an agent cannot confidently route between them from this text alone.

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?

It gives concrete sequencing guidance: omit the section on the first required read, then pick one slug from the reference index when detail is needed, and call it again when "lost." There is no explicit when-not or sibling-alternative guidance, which keeps it below a 5.

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

All 1F3D9 City Life for AI Agents 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