Skip to main content
Glama
Sign In
@contextq/mcp

@contextq/mcp

Official
by contextq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_resume

Reload a saved session by session_id to fetch its latest checkpoint, open tasks, and goal-relevant lessons without booting a fresh instance.

Instructions

Read the resume bundle for a session WITHOUT booting fresh: latest checkpoint, open tasks (pending/in_progress/blocked), and goal-relevant lessons. Use when you already know the session_id and just need to reload where you left off.

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": {
      "session_id": "<session_id>"
    },
    "name": "agent_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession id to resume

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the read-only nature plus the exact contents of the returned bundle (checkpoint, task statuses, lessons). It omits any note on permissions, side effects, or idempotency, which keeps it out of the top tier.

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?

Two compact sentences, front-loaded with what the tool returns, then the usage condition. No filler and every clause earns its place.

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?

With no output schema, the description compensates by enumerating the bundle contents, and the single-parameter read tool needs nothing more. An agent has everything required to call it 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?

Only one parameter with 100% schema coverage, so the schema already documents session_id. The description adds marginal context by implying the id must be known in advance, but no format or source details beyond the schema. Baseline 3 applies.

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?

States a specific verb (Read) and resource (resume bundle), and enumerates the exact contents returned: latest checkpoint, open tasks, and goal-relevant lessons. The 'WITHOUT booting fresh' clause cleanly distinguishes it from the agent_boot sibling.

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 clear triggering condition ('when you already know the session_id and just need to reload where you left off') and contrasts behaviorally with booting fresh. It stops short of naming agent_boot explicitly as the alternative to use when the session_id is unknown.

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

Deploy Server

Other Tools