Skip to main content
Glama

Cubite LMS: Learning Management System

Fetch a search result

fetch
Read-only

Read one result found via search as plain text with its public page URL, for quoting or citing it in an answer; this is the fetch half of the search/fetch pair. Pass the result's id exactly as search returned it (e.g. "course:..."). Returns {id, title, text, url, metadata}. A course's text is its public catalog summary (name, description, level, duration in hours, price, subjects, topics), not its lessons. A missing document, another site's content, and a type this connection cannot read all return the same not-found error; an id without a type prefix is rejected as invalid. To work with a course rather than quote it, use course_get for its settings record (ids, flags, dates, enrollment count) and course_content_get for its lessons as EditorJS blocks.

Input Schema

NameRequiredDescriptionDefault
idYesA document id exactly as `search` returned it, including its type prefix.

Output Schema

NameRequiredDescriptionDefault
idYesThe document id that was fetched.
urlYesPublic URL (used for citations).
textYesFull readable text of the document.
titleYesDocument title.
metadataNoExtra key/value details (entity type, dates).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, non-open-world), and the description adds behavior the annotations cannot: the exact return shape, the error-collapsing rule (missing doc, foreign site, unreadable type all yield the same not-found), the invalid-id rejection, and that a course's text is the catalog summary rather than its lessons.

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?

Front-loaded with purpose then progressively adding format, return, error, and alternative guidance — each sentence carries information. Slight redundancy in restating the return shape `{id, title, text, url, metadata}` when an output schema already exists.

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?

Covers purpose, parameter format, return content, error semantics, and sibling routing. With an output schema present, no further explanation of return values is required, so nothing material is missing.

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 documents `id`. The description still adds real value: it must be passed exactly as search returned it, needs the type prefix, and a prefix-less id is rejected as invalid — format constraints beyond the schema text.

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 (read one result) plus resource (a result previously found via `search`) and names the pair relationship with `search`. It also distinguishes itself from the course-oriented siblings by framing output as plain text with a public page URL for quoting/citing.

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?

Explicitly gives the when ('for quoting or citing it in an answer') and the when-not with named alternatives: 'To work with a course rather than quote it, use course_get ... and course_content_get for its lessons.' The agent has a clear routing rule.

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