Skip to main content
Glama
dcostenco

Prism MCP

by dcostenco
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

session_load_context

Recover previous work state by loading session context for a project. Choose from three levels: quick for latest state, standard for summaries, or deep for full history.

Instructions

Load session context for a project using progressive context loading. Use this at the START of a new session to recover previous work state. Three levels available:

  • quick: Just the latest project state — keywords and open TODOs (~50 tokens)

  • standard: Project state plus recent session summaries and decisions (~200 tokens, recommended)

  • deep: Everything — full session history with all files changed, TODOs, and decisions (~1000+ tokens)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoOptional. Agent role for Hivemind scoping (e.g., 'dev', 'qa', 'pm'). Omit to let the server auto-resolve from dashboard settings. When set, also injects active_team roster.
levelNoHow much context to load: 'quick' (just TODOs), 'standard' (recommended — includes recent summaries), or 'deep' (full history). Default: standard.
promptNoOptional. User prompt text for keyword-triggered skill loading. When provided, the server matches against prompt_keywords in the routing table and loads additional skills. Fires on every call — enables mid-session re-routing when the user's focus changes.
projectYesProject identifier to load context for.
max_tokensNoMaximum token budget for context response. Uses 1 token ≈ 4 chars heuristic. When set, the response is truncated to fit within the budget. Default: unlimited.
toolActionYesBrief 2-5 word summary of what this tool is doing. Capitalize like a sentence.
toolSummaryYesBrief 2-5 word noun phrase describing what this tool call is about.
conversation_idNoOptional. Session key for this conversation (same id used in session_save_ledger). When provided, marks the session as context-loaded server-side so project-scoped tools can verify working context without relying on hook-based enforcement. Required on non-Claude hosts.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv15.2.2
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Optional. Session key for this conversation (same id used in session_save_ledger). When provided, marks the session as context-loaded server-side so project-scoped tools can verify working context without relying on hook-based enforcement. Required on non-Claude hosts.",
+  "type": "string"
+}
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Optional. User prompt text for keyword-triggered skill loading. When provided, the server matches against prompt_keywords in the routing table and loads additional skills. Fires on every call — enables mid-session re-routing when the user's focus changes.",
+  "type": "string"
+}
  2. Addedv15.2.1
  3. Removedv2.3.38
  4. Addedv2.3.34
  5. Removedv2.3.33
  6. Changed2 schema fields changedv2.3.17
    • addedInput schema / properties / max_tokens
      Added value: +{
+  "description": "Maximum token budget for context response. Uses 1 token ≈ 4 chars heuristic. When set, the response is truncated to fit within the budget. Default: unlimited.",
+  "type": "integer"
+}
    • changedInput schema / properties / role / description
      Previous value: -"v3.0: Agent role for Hivemind scoping (e.g., 'dev', 'qa', 'pm'). Defaults to 'global'. When set, also injects active_team roster."New value: +"Optional. Agent role for Hivemind scoping (e.g., 'dev', 'qa', 'pm'). Omit to let the server auto-resolve from dashboard settings. When set, also injects active_team roster."
  7. Changed1 schema field changedv2.3.15
    • addedInput schema / properties / role
      Added value: +{
+  "description": "v3.0: Agent role for Hivemind scoping (e.g., 'dev', 'qa', 'pm'). Defaults to 'global'. When set, also injects active_team roster.",
+  "type": "string"
+}
  8. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description must bear the full burden. It discloses three context loading levels with token costs and mentions progressive loading. However, it does not detail permissions, side effects, or whether it modifies state (likely not, as it's loading).

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?

The description is concise, front-loaded with the main purpose, and uses a bulleted list for the three levels. Every sentence adds value without waste.

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 the tool's complexity (progressive loading, multiple parameters, enum), the description covers the main use case and token budgets. It lacks an output schema but mentions truncation behavior, making it sufficient for an agent to invoke correctly.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds some value by explaining the three levels in narrative form and recommending 'standard', but the schema already describes each parameter adequately. The description does not significantly supplement parameter meaning beyond what the schema provides.

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 loads session context for a project using progressive context loading. It specifies it should be used at the start of a new session to recover previous work state, distinguishing it from siblings like session_save_ledger or session_compact_ledger.

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?

The description explicitly says to use this at the START of a new session and recommends the 'standard' level. It provides clear context but does not explicitly state when not to use it or mention alternatives among the many sibling session tools.

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/dcostenco/prism-coder'

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