Skip to main content
Glama

Estimate walking time between buildings

estimate_walk_time
Read-only

Estimate walking time between CMU Pittsburgh buildings using room or building names to check tight class passing periods; offline straight-line estimate, not navigation.

Instructions

Offline estimate of the walk between two CMU Pittsburgh buildings. Accepts room strings ("GHC 4401", "DH A302", "Wean Hall 7500") or bare building names/codes. Rooms are not in the public schedule, so they come from the student (SIO). Straight-line distance between building centroids x 1.4 for real paths, at 80 m/min: for spotting tight passing periods, not navigation.

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": {
      "from_location": "<from_location>",
      "to_location": "<to_location>"
    },
    "name": "estimate_walk_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_locationYesWhere the later class meets, e.g. "DH 2210" or "Posner".
from_locationYesWhere the earlier class meets, e.g. "GHC 4401" or "Baker Hall".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses that the estimate is offline, the actual method (centroid straight-line distance x 1.4 for real paths at 80 m/min), and that precision is approximate. It also flags a real data dependency — room strings are not in the public schedule and must come from the student (SIO) — which is exactly the kind of caveat an agent needs.

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?

Front-loads the purpose, then packs accepted formats and the algorithm into short clauses with no filler. Density is high enough that the accuracy caveat and the SIO provenance note require a careful read, but nothing is redundant.

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?

There is no output schema, yet the description gives the basis of the number (80 m/min over inflated straight-line distance) so the agent can interpret the result. It stops short of stating the return unit or format explicitly and does not describe failure behavior for unrecognized buildings.

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 already 100% with examples for both fields, so the baseline is 3; the description adds value by accepting either room strings ('GHC 4401', 'DH A302', 'Wean Hall 7500') or bare building names/codes, widening the accepted input beyond what the schema examples suggest. It does not, however, say what happens if a room cannot be resolved.

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 and resource ('offline estimate of the walk between two CMU Pittsburgh buildings') and pins the scope to campus buildings, so it is clearly distinct from search_courses and list_buildings. An agent can tell what it returns without opening the schema.

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?

Explicitly frames the intended use ('for spotting tight passing periods, not navigation') and the inputs are class-meeting locations, which implies the workflow. It does not name a sibling tool or state when to prefer listing buildings instead, so routing guidance is contextual rather than explicit.

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