Skip to main content
Glama

List Degrees

list-degrees
Read-onlyIdempotent

List the degrees taught at a high school, with their ids, so you can pass degree_id to search-courses. The ids are national, so search-courses can use them with no school. Pass institution_id from search-institutions. A university id is not a high school. Each degree may include grades with grade ids. When grades are not listed, take grade_id from a search-courses result. Show the user the degree and grade names, not the ids.

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": {
      "institution_id": "<institution_id>"
    },
    "name": "list-degrees"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_idYesNumeric high-school id from search-institutions (the id field). Example: 42. A university id does not list degrees.

Output Schema

NameRequiredDescriptionDefault
degreesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add domain behavior, which it does: degree ids are national and usable without school context, grades may or may not be embedded, and a university id yields no degrees. It stops short of saying what an invalid or empty result looks like, so it is not fully exhaustive.

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?

Five short sentences, front-loaded with purpose and downstream routing. Minor redundancy: the 'university id is not a high school' point appears twice in the description and again in the schema, and part of the wording is display guidance rather than tool semantics.

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?

For a one-parameter read tool with an output schema, this covers the prerequisite source, the downstream consumer, the cross-school id property, the optional grades payload, and a display instruction (show names, not ids). Nothing an agent needs in order to call it correctly is missing.

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 parameter already documents its source, example, and the university-id caveat. The description restates the same provenance and caveat rather than adding format or edge-case meaning beyond the schema, so baseline 3 applies.

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 degrees taught at a high school') plus the immediate downstream use ('so you can pass degree_id to search-courses'). It also carves out the boundary that a university id is not valid, which distinguishes this from institution-level siblings.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite chain: get institution_id from search-institutions, then feed the resulting degree_id into search-courses. It also names an exclusion (university ids don't list degrees) and a fallback rule (when grades aren't listed, take grade_id from a search-courses result).

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