Skip to main content
Glama

Search Courses

search-courses
Read-onlyIdempotent

Find a course on Studocu by name or code, to get its course_id for search-documents, get-course-syllabus, or get-course-mastery. Pass institution_id from search-institutions when you know the school. For a high school, pass degree_id and grade_id from list-degrees. Those ids are national, so a school is optional. With a school, the level filter is added to that school search. Ids only, not names. Pass include_levels: true to include degree and grade on every course. A course whose institution_id is null cannot be used to create or update a project. Prefer a course with an institution_id, or ask the user to pick their school. Show the user the name, code, school, degree, and grade, not the ids. If several results are plausible, ask the user to pick.

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": "search-courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many courses to return. Integer from 1 to 10. Default 3.
queryYesCourse name or code, 1-200 characters after trimming. Example: "ECON101" or "Introduction to Psychology".
grade_idNoNumeric national high-school grade id, taken from list-degrees (grades[].id) or from grade.id on a search-courses result. Never guess it and never pass the grade name. A school is optional. Omit if unknown.
degree_idNoNumeric national high-school degree id, taken from list-degrees (the id field) or from degree.id on a search-courses result. Never guess it and never pass the degree name. A school is optional. Matches courses of that degree and courses of its grades. Omit if unknown.
include_levelsNoSet true to include degree and grade on every course. Omit for the legacy payload.
institution_idNoNumeric school id from search-institutions (the id field). Example: 42. Omit to search every school. Prefer setting it when you already know the school.

Output Schema

NameRequiredDescriptionDefault
coursesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / degree_id
      Added value: +{
      +  "description": "Numeric national high-school degree id, taken from list-degrees (the id field) or from degree.id on a search-courses result. Never guess it and never pass the degree name. A school is optional. Matches courses of that degree and courses of its grades. Omit if unknown.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 2147483647,
      +  "type": "integer"
      +}
    • addedInput schema / properties / grade_id
      Added value: +{
      +  "description": "Numeric national high-school grade id, taken from list-degrees (grades[].id) or from grade.id on a search-courses result. Never guess it and never pass the grade name. A school is optional. Omit if unknown.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 2147483647,
      +  "type": "integer"
      +}
    • addedInput schema / properties / include_levels
      Added value: +{
      +  "description": "Set true to include degree and grade on every course. Omit for the legacy payload.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / courses / items / properties / degree
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "id": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / courses / items / properties / grade
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "degree_id": {
      +          "anyOf": [
      +            {
      +              "maximum": 9007199254740991,
      +              "minimum": -9007199254740991,
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "id": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "degree_id"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / courses / items / properties / institution_id / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / courses / items / properties / institution_id / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / courses / items / properties / institution_id / minimum
      Removed value: --9007199254740991
    • removedOutput schema / properties / courses / items / properties / institution_id / type
      Removed value: -"integer"
  2. Changed3 schema fields changed
    • addedInput schema / properties / institution_id / description
      Added value: +"Numeric school id from search-institutions (the id field). Example: 42. Omit to search every school. Prefer setting it when you already know the school."
    • addedInput schema / properties / limit / description
      Added value: +"How many courses to return. Integer from 1 to 10. Default 3."
    • addedInput schema / properties / query / description
      Added value: +"Course name or code, 1-200 characters after trimming. Example: \"ECON101\" or \"Introduction to Psychology\"."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior: a course with null institution_id cannot be used to create or update a project, so prefer one with an institution_id, and school filtering changes how the level filter is applied. It stops short of describing result ordering or pagination beyond the limit parameter.

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?

Purpose and downstream consumers are front-loaded, and the remaining sentences are short imperative fragments that each convey a distinct rule. It is dense but slightly list-like, with a small amount of redundancy around the optional school.

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 read-only search with a full input schema and an output schema, the definition supplies everything an agent needs: id provenance, optionality of the school, privacy guidance (show name/code/school/degree/grade, not ids), and disambiguation behavior.

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 100%, so the schema already carries parameter meaning; the description still adds cross-tool provenance (ids come from search-institutions and list-degrees), stresses 'Ids only, not names,' and explains when a school is optional. That is real added value over the schema, though include_levels is largely restated.

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 ('Find a course on Studocu by name or code') and immediately names the downstream tools that consume the returned course_id, which separates it cleanly from search-documents and search-institutions.

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?

Explicit routing rules: pass institution_id from search-institutions when the school is known, pass degree_id/grade_id from list-degrees for high schools, omit a school when unknown, and ask the user to pick when several results are plausible. This covers when-to-use and what to do under ambiguity.

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