uNotes

Search library

search_library

Read-onlyIdempotent

Search the public uNotes document library by title, course, or type keywords. Call it with the query alone whenever no scope id is already known — schoolId and courseId are optional narrowing hints, never prerequisites, and must never be requested from the user. Course codes and school names the user typed belong in the query text. It searches documents only: it is not for the user's own quizzes or flashcards, which have their own listing tools.

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

Input Schema

Name	Required	Description
`limit`	No	Max results to return
`query`	Yes	Search query (title keywords)
`courseId`	No	Optional course UUID taken from the active context. Never a course code like "MAT 1341" — those go in query.
`schoolId`	No	Optional school UUID taken from the active context. Never a school name and never asked for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedOct 5, 2026

TDQS

A4.1/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:false, so the safety profile is fully carried structurally. The description adds scope behavior annotations cannot express: results come from the public library only, and scope ids originate from active context rather than user prompting. It does not describe result shape or pagination, but no output schema exists so some of that burden remains.

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?

Three sentences, front-loaded with the verb and resource, and the most decision-relevant rule (query alone, ids optional) comes early. Mild redundancy with the schema's own parameter text, but no filler sentences.

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?

Four parameters, one required, full schema coverage and rich annotations mean the description only needs to cover scope and invocation strategy, which it does. What is missing is matching behavior detail (does query hit title only, or also course/type, and how limit interacts with result quality).

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 schema already states that courseId must be a UUID from context with course codes going in query, and that schoolId is a UUID never asked for. The description restates those same rules rather than adding new semantics, so this is reinforcement, not new information. Baseline 3 applies.

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?

States a specific verb and resource with scope: "Search the public uNotes document library by title, course, or type keywords." It also bounds the domain by excluding the user's own quizzes and flashcards. It stops short of distinguishing itself from the very close sibling find_documents, which an agent would likely weigh against it.

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 invocation rule: "Call it with the query alone whenever no scope id is already known," with schoolId/courseId framed as optional narrowing hints and "never prerequisites... never requested from the user." Negative case is also given ("not for the user's own quizzes or flashcards, which have their own listing tools"). Only the find_documents alternative is unaddressed.

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

All uNotes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?