Skip to main content
Glama

Find Programs

find_programs
Read-only

Which programs match these words, across institutions? The words are read in each program's name and award title, its description, and its CIP's title and definition, and the programs come back in that order (name and award matches first). Optionally one institution's UNITID, a state or a city. Each program answers with its award, its CIP code with the CIP's title and definition, its published credit figure verbatim, edition, source page and institution. Each row names its current FORM's wording source: source_url, capture_file, catalog_year and source_catalog_name are that one source's, never the record's whole span. A row whose record holds more than one form or more than one source also carries version_count, source_count, first_edition_seen and last_edition_seen, and one sentence saying so in words; a record with one form and one source carries none of them and reads exactly as it always has. The forms themselves, each with its own content and its own sources, come from the one-record get, never from a list. A record last seen in an older edition says so, because the Union keeps a record no current catalog prints.

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": {
      "query": "<query>"
    },
    "name": "find_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city: programs at that city's institutions
limitNoOptional page size (default 20, at most 100)
queryYesWords, e.g. welding, nursing or computer: read in names, award titles, descriptions and the CIP's title and definition
stateNoOptional two-letter state: programs at that state's institutions
offsetNoOptional: the next_offset from a previous answer
unitidNoOptional: one institution's IPEDS UNITID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Program or award words, e.g. welding or nursing"New value: +"Words, e.g. welding, nursing or computer: read in names, award titles, descriptions and the CIP's title and definition"
  2. Changed2 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "Optional city: programs at that city's institutions",
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Optional two-letter state: programs at that state's institutions",
      +  "type": "string"
      +}
  3. Added

TDQS

A3.8/5.0
Behavior5/5

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

With only readOnlyHint in annotations, the description carries substantial behavioral detail: it explains match fields, result ordering, row payload, source-scope semantics, conditional version/source fields, and the behavior for records last seen in an older edition. This is exactly the kind of context an agent needs beyond the structured annotations.

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

Conciseness3/5

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

The first sentence is front-loaded and effective, and most later sentences add useful behavioral detail. However, the description is long and includes dense, somewhat run-on phrasing that could be tightened without losing meaning.

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, so the description appropriately explains the returned program row, conditional fields, source fields, and edition behavior. It is largely complete for a complex search tool, though it does not discuss pagination behavior beyond what the schema covers.

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 description coverage is 100%, so the schema already documents all six parameters well. The description mentions the optional UNITID, state, and city filters but adds little semantic detail beyond what those schema descriptions already provide.

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?

The description clearly states that this tool searches programs by words across institutions and explains which fields are searched, making the resource and operation identifiable. It also differentiates itself from the one-record get for forms, though it does not explicitly distinguish itself from the closest search sibling, search_programs_and_learning_units.

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 implied through the optional filters and the note that full form content comes from the one-record get, not this list. However, there is no explicit guidance on when to choose this tool over nearby alternatives such as search_programs_and_learning_units or programs_for_institution.

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.