Skip to main content
Glama

Get Learner Context

get-context
Read-onlyIdempotent

Load the learner's profile, followed courses, and projects. Use get-project-state for what is inside a project. Per-topic practice scores are included only when one course is in scope; otherwise use get-course-mastery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-context"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idNoReturn only this course and its projects. Numeric id or the same id as text. Example: 1581710 or "1581710". Omit to include every followed course.
project_idNoReturn only this project. Example: "11111111-1111-4111-8111-111111111111". From an earlier get-context or create-project result. Omit to include the learner's projects.
active_onlyNoOptional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it.
recent_onlyNoOptional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it.

Output Schema

NameRequiredDescriptionDefault
dataYes
aggregatesNo
generated_atYes
prompt_viewsNo
requested_filtersYes
context_schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / data / properties / projects / items / properties / metadata / properties / url
      Added value: +{
      +  "description": "Studocu web link to the project. Share it with the user.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / active_only / description
      Previous value: -"Limit the manifest to active context."New value: +"Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it."
    • changedInput schema / properties / course_id / description
      Previous value: -"Narrow context to a single followed course and its projects."New value: +"Return only this course and its projects. Numeric id or the same id as text. Example: 1581710 or \"1581710\". Omit to include every followed course."
    • changedInput schema / properties / project_id / description
      Previous value: -"Narrow context to a single project by id."New value: +"Return only this project. Example: \"11111111-1111-4111-8111-111111111111\". From an earlier get-context or create-project result. Omit to include the learner's projects."
    • changedInput schema / properties / recent_only / description
      Previous value: -"Limit the manifest to recently active context."New value: +"Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds a genuinely non-obvious behavioral trait: per-topic practice scores appear conditionally, only when a single course is in scope. It does not note that active_only/recent_only are echoed no-ops, but the schema states that explicitly.

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 short sentences, zero filler, with the primary purpose front-loaded ahead of the alternative-routing advice. Every sentence carries distinct information.

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?

For a read-only context loader with full annotation coverage, complete schema descriptions, and an output schema, nothing material is missing. Scope, alternatives, and the one conditional output nuance are all stated.

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 baseline is 3 and the schema carries the parameter documentation. The description still adds meaning by explaining the scoping consequence of narrowing to one course — that per-topic practice scores become available — which is not implied by the course_id description alone.

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 and enumerates the exact resources loaded: the learner's profile, followed courses, and projects. It immediately distinguishes this breadth-first tool from get-project-state, so an agent can tell the two apart without reading either schema.

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?

It names two concrete alternatives with the conditions that select them: get-project-state when you need project internals, and get-course-mastery when more than one course is in scope. The routing decision is left to nothing but inference.

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