Skip to main content
Glama

Get Syllabus

get_syllabus
Read-only

Reads a course syllabus to check its AI-use and collaboration policy before helping with graded work, ensuring assistance follows course rules.

Instructions

Reads a course's syllabus. Check it for the course's policy on AI use and collaboration before helping with graded work, and follow that policy.

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": {
      "course_id": "<course_id>"
    },
    "name": "get_syllabus"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which matches the 'Reads' verb, so no contradiction. The description contributes useful context about what the content governs (AI/collaboration policy) but says nothing about return format, failure modes, or what happens for unknown course ids.

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?

Two front-loaded sentences with no filler; the core action comes first and the advisory instruction second. Slightly more could be trimmed but nothing is wasted.

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?

For a simple one-parameter read tool with annotations covering safety and no output schema, the description covers purpose and usage adequately. Only the return shape and the meaning of course_id remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single course_id parameter, so the description must carry the meaning. It only implies the parameter identifies a course via 'a course's syllabus' and adds no format, range, or lookup detail beyond what the integer schema states.

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+resource: 'Reads a course's syllabus.' An agent can tell this apart from get_assignment or read_course_page by the resource named, though it never explicitly contrasts with those siblings.

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?

Gives a concrete usage trigger: check the syllabus for the AI-use and collaboration policy before helping with graded work, and follow that policy. It is clear about when to call it but offers no exclusions or named alternatives.

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