Skip to main content
Glama

advancedcontext

Query and analyze your educational knowledge graph to retrieve course details, track deadlines, prepare for exams, and explore concept relationships for effective academic planning.

Instructions

A comprehensive tool for querying and analyzing your educational knowledge graph. This tool provides specialized operations to extract meaningful insights and contextual information about your academic journey. It enables deep exploration of courses, assignments, exams, concepts, and educational resources.

When to use this tool:

  • Retrieving the complete educational knowledge graph

  • Searching for specific academic entities using keyword matching

  • Fetching details on a precise set of educational entities

  • Getting comprehensive information about a specific course

  • Finding upcoming assignment and exam deadlines

  • Checking detailed status of a specific assignment

  • Preparing for exams with concept retrieval

  • Discovering connections between learning concepts

  • Tracking and reviewing lecture notes

  • Getting an overview of an entire academic term

  • Identifying entities by status (not_started, in_progress, complete)

  • Finding high-priority assignments and tasks

  • Exploring sequential relationships between entities

Key features:

  • Ten specialized query operation types

  • Full educational graph retrieval with entities and relations

  • Keyword-based search across academic entities and their properties

  • Direct entity lookup by exact name

  • Course details including lectures, assignments, exams, and resources

  • Deadline tracking with time-based filtering

  • Assignment status with progress tracking through has_status relations

  • Priority information via has_priority relations

  • Exam preparation with related concepts and materials

  • Concept relationship mapping

  • Sequential entity relationships via follows relations

  • Lecture note organization

  • Term-based academic overview

  • JSON-formatted response with query results

Parameters explained:

  • type: The query operation type to perform, which must be one of:

    • "graph" - Retrieve the entire educational knowledge graph

    • "search" - Find academic entities by keyword/partial match

    • "nodes" - Get specific educational entities by exact name

    • "course" - Get comprehensive details about a specific course

    • "deadlines" - Get upcoming assignment and exam deadlines

    • "assignment" - Get detailed status of a specific assignment

    • "exam" - Get preparation materials for a specific exam

    • "concepts" - Find related concepts based on a starting concept

    • "lecture" - Track and organize notes for lectures

    • "term" - Get overview of an academic term

  • params: Operation-specific parameters structure:

    • For "graph": No parameters needed

    • For "search": { query: "search text" }

    • For "nodes": { names: ["EntityName1", "EntityName2", ...] }

    • For "course": { courseName: "Course Name" }

    • For "deadlines": { termName: "Term Name", courseName: "Course Name", daysAhead: 14 }

    • For "assignment": { assignmentName: "Assignment Name" }

    • For "exam": { examName: "Exam Name" }

    • For "concepts": { conceptName: "Concept Name", depth: 1 }

    • For "lecture": { courseName: "Course Name" }

    • For "term": { termName: "Term Name" }

Operation details:

  • "graph" returns the complete educational knowledge graph structure

  • "search" performs partial matching on entity names, types, and observations

  • "nodes" retrieves specific entities by exact name matching

  • "course" provides a comprehensive view of a course with its components

  • "deadlines" finds upcoming assignments and exams with due dates

  • "assignment" shows detailed status and related concepts for an assignment

  • "exam" provides study resources and related concepts for exam preparation

  • "concepts" maps relationships between different learning concepts

  • "lecture" organizes and retrieves notes for course lectures

  • "term" gives an overview of courses and work for an academic term

Status information:

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

  • Status can be used in search queries (e.g., "status:complete")

  • Course views show assignment completion status

  • Term views highlight course completion percentages based on status

Priority information:

  • Entities can have priority values (low, high) via has_priority relations

  • Priority can be used in search queries (e.g., "priority:high")

  • High-priority items are highlighted in course and term views

Sequential relationships:

  • Entities can have sequence relationships through follows relations

  • Course views show recommended sequence of assignments and lectures

  • Concept views show prerequisite relationships

Return structures:

  • All operations return { success: true/false, ... } with operation-specific data

  • Error responses include detailed error messages

  • Complex operations return rich, structured data about academic entities

  • Educational relationships are preserved in all returned data

  • Status and priority information is included in relevant entity data

You should:

  1. Select the most appropriate query type for your educational information need

  2. Provide the required parameters for your chosen operation type

  3. Start with broader queries and refine to more specific ones

  4. Use "search" for exploratory investigation of your academic knowledge

  5. Use "course" to get a comprehensive view of your coursework

  6. Use "deadlines" to stay on top of upcoming academic work

  7. Use "concepts" to understand relationships between learning topics

  8. Filter search results by status to focus on incomplete work

  9. Prioritize assignments based on priority values

  10. Follow sequential relationships to create effective study plans

  11. Combine query results to build comprehensive study strategies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesParameters for the operation, structure varies by type
typeYesType of get operation: 'graph', 'search', 'nodes', 'course', 'deadlines', 'assignment', 'exam', 'concepts', 'lecture', or 'term'
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by detailing return structures ('All operations return { success: true/false, ... }'), error handling ('Error responses include detailed error messages'), data relationships ('Educational relationships are preserved'), and specific behaviors like status/priority filtering capabilities. It doesn't mention rate limits or authentication requirements, keeping it from a perfect score.

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

Conciseness3/5

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

While well-structured with clear sections, the description is excessively long (over 700 words) with repetitive information. The 'Operation details' section largely repeats what's already in 'Parameters explained,' and the 'You should' section could be more concise. Every sentence doesn't earn its place given the redundancy.

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 complex tool with 10 operation types, no annotations, and no output schema, the description provides comprehensive context. It covers purpose, usage scenarios, parameter semantics, behavioral details, return structures, and practical guidance. The agent has everything needed to select and invoke this tool correctly despite the missing structured metadata.

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?

Despite 100% schema description coverage, the description adds substantial value with a detailed 'Parameters explained' section that clarifies each operation type's purpose and provides concrete examples of the params structure for every type. This transforms the schema's generic 'object' parameter into actionable guidance for the agent.

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 'querying and analyzing your educational knowledge graph' with 'specialized operations to extract meaningful insights and contextual information about your academic journey.' It distinguishes from siblings like 'buildcontext' and 'deletecontext' by focusing on query/analysis rather than creation or deletion operations.

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 provides explicit guidance with a 'When to use this tool' section listing 13 specific scenarios, plus a numbered 'You should' section with 11 actionable recommendations. It distinguishes when to use specific operation types (e.g., 'Use "search" for exploratory investigation' vs 'Use "course" to get a comprehensive view').

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