Skip to main content
Glama

List known CMU buildings

list_buildings
Read-only

Retrieve CMU buildings with Schedule of Classes codes, alternate names, and approximate coordinates; filter by code, name, or alias to identify locations for scheduling and walking-time estimates.

Instructions

Every CMU building estimate_walk_time knows, with the Schedule of Classes building code, alternate names and approximate coordinates (© OpenStreetMap contributors, ODbL).

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": "list_buildings"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOnly buildings whose code, name or aliases contain this text, e.g. "hall".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds context beyond that: the list is exactly the set known to estimate_walk_time, it includes the Schedule of Classes code plus aliases and approximate coordinates, and the data source/licence (OpenStreetMap, ODbL) is disclosed — useful for judging accuracy and attribution.

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?

One dense sentence that front-loads the core claim (every building known to estimate_walk_time) and appends the returned fields and attribution. Nothing is wasted, though the licence parenthetical is more for correctness than for agent selection.

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 usefully names the returned fields (code, aliases, approximate coordinates) and the scope of the result set. For a single-optional-param read-only list tool this is nearly complete; only ordering/pagination or result-size expectations are unstated.

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 single optional 'search' parameter is fully documented in the schema (substring match on code, name or aliases). The description adds no parameter detail, which is acceptable given the schema does the work, so the baseline of 3 applies.

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+resource (list all CMU buildings) and enumerates the returned fields (building code, alternate names, coordinates), and ties the set to estimate_walk_time's knowledge. It is clear what the tool does, though it doesn't name a sibling it is distinct from in when-to-use terms.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of estimate_walk_time hints this is a lookup for building codes/coordinates used by the walk-time tool. There is no explicit when-to-use or when-not-to-use statement, and no mention that search can be used to narrow results.

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