Skip to main content
Glama

loadcontext

Retrieve structured academic details for courses, assignments, exams, and concepts. Track deadlines, study resources, and progress to plan effectively and stay organized.

Instructions

A powerful tool for retrieving comprehensive, structured information about specific educational entities, providing context-rich details tailored to academic needs.

When to use this tool:

  • Retrieving detailed information about courses, assignments, exams, and academic concepts

  • Exploring course materials, lecture schedules, and assignment deadlines

  • Preparing for upcoming exams by identifying key concepts and resources

  • Tracking assignment status and due dates

  • Understanding relationships between academic concepts

  • Examining course structures and learning resources

  • Planning study sessions around specific courses or topics

  • Reviewing term schedules and upcoming deadlines

  • Organizing academic resources by courses and concepts

  • Establishing context for effective learning and study planning

  • Viewing entity status information (not_started, in_progress, complete)

  • Checking priority levels for assignments and tasks

  • Understanding sequential relationships between academic entities

Key features:

  • Provides richly formatted, context-aware information about educational entities

  • Adapts output format based on entity type (course, assignment, exam, concept, term)

  • Presents both direct entity information and related academic elements

  • Shows time-sensitive information like due dates and exam schedules

  • Tracks loaded entities within the current session for continuity

  • Formats information in a clean, readable markdown structure

  • Automatically identifies relationships between academic entities

  • Displays status information via has_status relations

  • Shows priority levels via has_priority relations

  • Presents sequential relationships through follows relations

  • Highlights status of assignments and upcoming deadlines

  • Shows progress metrics for courses and assignment completion

Parameters explained:

  1. entityName: Required - The name of the entity to retrieve context for

  • Example: "Introduction to Computer Science", "Midterm Paper", "Binary Trees"

  1. entityType: Optional - The type of entity being retrieved

  • Default: "course"

  • Accepts values from valid entity types for the student domain

  • Helps the system format the output appropriately

  1. sessionId: Optional - The current session identifier

  • Typically provided by startsession

  • Used for tracking entity views within the session

Each entity type returns specialized context information:

  • Course: Shows code, status (via has_status), schedule, location, description, professor information, lectures, assignments (with status and priority), exams, key concepts, and resources

  • Assignment: Displays course, status (not_started, in_progress, complete), priority (low, high), due date, points, time remaining, instructions, related concepts, helpful resources, and your notes

  • Exam: Shows course, date, time remaining, location, format, duration, concepts to study, key lectures, and study resources

  • Concept: Displays difficulty level, description, related concepts (including sequential relationships), courses covering this concept, and learning resources

  • Term: Shows start date, end date, status, courses for the term (with completion percentages), and upcoming deadlines

  • Other Entity Types: Shows observations and both incoming and outgoing relationships within the knowledge graph

Status and Priority:

  • All entities include status values (not_started, in_progress, complete) retrieved via has_status relations

  • Relevant entities include priority values (low, high) retrieved via has_priority relations

  • Status information is used to calculate completion percentages and filter assignments

  • Priority information helps identify important tasks and assignments

Sequential Relationships:

  • Related entities may have follows relationships indicating recommended sequence

  • Course view shows sequenced lectures and assignments

  • Concept view shows prerequisite relationships between concepts

Return information:

  • Formatted markdown text with hierarchical structure

  • Sections adapted to the specific entity type

  • Related entities shown with their status, priority, and descriptions

  • Error messages if the entity doesn't exist or can't be retrieved

You should:

  • Specify the exact entity name for accurate retrieval

  • Provide the entity type when possible for optimally formatted results

  • Start with course entities to get a high-level overview of academic materials

  • Use assignment context to track deadlines and submission status

  • Prepare for exams by examining exam context for study resources

  • Explore concept context to understand relationships between academic topics

  • Review term context to plan your academic schedule

  • Pay attention to status values to identify incomplete assignments

  • Consider priority information when planning your study schedule

  • Follow sequential relationships to create effective learning paths

  • After retrieving context, follow up on specific entities of interest

  • Use in conjunction with startsession to maintain session tracking

  • Combine with endsession to document your learning progress

  • Remember that this tool only retrieves existing information; use buildcontext to add new entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityNameYes
entityTypeNoType of entity to load, defaults to 'course'
sessionIdNoSession ID from startsession to track context loading
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly explains the tool's behavior, including output formatting (markdown), session tracking, entity type adaptations, and relationships like status and priority. However, it lacks details on error handling or rate limits, which are minor gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long and repetitive, with sections like 'Key features' and 'You should' that reiterate points already covered. While structured, it includes unnecessary details (e.g., listing all entity type outputs) that could be condensed, reducing efficiency for the agent.

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?

Given the tool's complexity (3 parameters, no annotations, no output schema), the description is highly complete. It covers purpose, usage, parameters, behavior, output format, and relationships with sibling tools, providing all necessary context for effective agent use without relying on structured fields.

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

Parameters5/5

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

The description includes a detailed 'Parameters explained' section that adds significant meaning beyond the input schema. It explains each parameter's purpose, provides examples, and clarifies defaults and usage, compensating for the 67% schema description coverage and enriching the agent's understanding.

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 clearly states the tool's purpose as 'retrieving comprehensive, structured information about specific educational entities' with 'context-rich details tailored to academic needs.' It distinguishes itself from sibling tools like buildcontext (for adding new entities) and deletecontext, making its retrieval-only function explicit.

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?

The description includes an explicit 'When to use this tool' section with 13 specific scenarios, such as retrieving course details or tracking assignments. It also provides guidance on when not to use it (e.g., 'use buildcontext to add new entities') and mentions alternatives like startsession for session tracking, ensuring clear differentiation from siblings.

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

Related 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/tejpalvirk/student'

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