Nexus MCP

Overview Schema Source Related Servers Discussions Admin

search_course_materials

Read-onlyIdempotent

Find course materials by title, filename, description, or section name across current or selected courses. Returns titles, types, URLs, and material IDs for retrieval without downloading files.

Instructions

Search course materials (PDFs, files, pages, books, links, folders, lecture notes) by title, filename, description or section name across current courses (or one course). Returns title, course, type, description, url and a material id for get_material. Nothing is downloaded by this call.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`course_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine extra context with the negative behavior "Nothing is downloaded by this call," which clarifies that matching files are not fetched. Pagination/limit behavior is left unstated, keeping it from a 5.

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?

Three sentences, each earning its place: purpose/scope first, return fields second, the "nothing is downloaded" caveat last. Zero waste and front-loaded with the essential action.

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 an output schema present, the return-value enumeration is a bonus rather than a necessity, and the annotations cover safety. The description routes the agent to get_material and states scope, leaving only the limit parameter's behavior undocumented.

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 description coverage is 0%, so the description must carry the load. It meaningfully explains query semantics ("by title, filename, description or section name") and course_id scoping ("across current courses (or one course)"), but the limit parameter is never addressed, so it compensates for two of three parameters.

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?

The description opens with a specific verb+resource ("Search course materials"), enumerates what counts as a material (PDFs, pages, books, links, folders, lecture notes), and states the searchable fields. It also distinguishes itself from the sibling get_material by noting it returns a material id for that tool, so an agent can separate discovery from retrieval.

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?

The description gives clear scope ("across current courses (or one course)") and a routing hint toward get_material via the returned id, implying a search-then-fetch workflow. It stops short of an explicit when-to-use/when-not statement or naming any alternative search tool, so it earns a solid 4 rather than a 5.

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