Skip to main content
Glama

List campuses

list_campuses
Read-onlyIdempotent

List the campuses where Fold offers a Semester Pass (prepaid weekly laundry pickup for college students). Returns four campuses — UCLA, USC, UC Berkeley, UCSF — each with their available terms (e.g. "Fall 2026"), the weekly pickup day, and pricing for both weekly and bi-weekly cadence. buy_semester_pass takes a campusId and termId from this list. Prices are in USD.

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_campuses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: it pins the result to exactly four named campuses and discloses that prices are in USD, which annotations cannot convey. Minor gap: no mention of caching/staleness or whether terms ever expire.

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?

Four short sentences, front-loaded with the core purpose, then return contents, then the sibling hand-off, then the currency note. Every sentence carries information an agent would otherwise have to discover by calling the tool.

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?

No output schema exists, and the description compensates by describing the returned fields (terms, pickup day, weekly/bi-weekly pricing) and the currency unit. For a trivial zero-param read with strong annotations, nothing an agent needs is missing.

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?

The tool takes zero parameters, so there is no input semantics to explain and the baseline is 4. The description instead names the downstream identifiers (campusId, termId) the returned objects expose, which is a useful bonus beyond a bare empty schema.

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 ("List the campuses where Fold offers a Semester Pass") and immediately scopes it with a parenthetical definition of the product. It also enumerates the exact return contents, so the agent knows precisely what this yields versus any other listing tool.

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 routes the agent forward: "buy_semester_pass takes a campusId and termId from this list," which is the primary reason to call this tool. It doesn't state any when-not conditions, but for a zero-param catalog read there is little ambiguity to exclude.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources