Skip to main content
Glama

Metis · Course Builder — Save Course Sources

save_course_sources

Save harvested source metadata for a course by passing a JSON array of source objects. Each source is written as a YAML file, advancing the build to the next step.

Instructions

Step 3 — Save harvested source metadata for a course.

Call this after the Content Harvester has collected materials. Pass a
JSON array of source objects. Each source is written as a YAML file in
`knowledge/courses/{slug}/sources/` and the build advances to Step 4.

Args:
    slug: The course slug.
    sources: JSON array of source dicts — each must have at least a
             ``title`` and one of ``url``, ``file_path``, or ``doi``.
             Example: '[{"title": "OpenIntro Stats", "url": "https://openintro.org/book/os/", "type": "textbook"}]'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
sourcesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses behavioral effects (writes YAML files, advances build) but does not cover error handling, idempotency, or prerequisite steps. Adequate but incomplete.

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?

Description is concise with front-loaded purpose, clear structure, and no unnecessary words. Each sentence adds value.

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?

Given 2 parameters, no annotations, and presence of output schema, description explains input format, effect, and pipeline position. Lacks error scenarios but is otherwise complete for a simple save tool.

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 0%, so description adds meaning: explains slug as course slug and sources as JSON array with required fields and an example. Significantly compensates for schema's lack of descriptions.

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?

Description states 'Step 3 — Save harvested source metadata for a course' with a specific verb and resource, and clearly distinguishes from sibling tools like save_course_curriculum and save_course_outline.

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?

Explicitly states 'Call this after the Content Harvester has collected materials', providing a clear precondition, and mentions that the build advances to Step 4, indicating sequence. Does not explicitly say when not to use, but the pipeline context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server