Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

resume_project

Resume a project by loading the plan and last handoff note to continue without losing context.

Instructions

Resume a Contextium project from a session handoff — loads the project plan, finds the last handoff note, and briefs you so you can continue without losing context. Call this when the user says things like: "resume my project", "continue where I left off", "pick up from last session", "what was I working on", "I'm back let's continue", "carry on from yesterday", "what's next in my project".

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": "resume_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowIdNoWorkflow ID to resume (optional — if omitted, auto-selects if only one workflow exists)
workspaceIdNoWorkspace ID (uses default if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so description must disclose side effects. It lists actions (loads, finds, briefs) but does not state whether it modifies state (e.g., marks handoff as read) or if it is a read-only operation. Lacks explicit behavioral cues.

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 sentences with a list of examples. No filler, front-loaded with key action. Every sentence adds value.

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?

Covers purpose and triggers well, but lacks details on return value or post-call state. For a tool with simple parameters and no output schema, this is sufficient but not exhaustive.

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 description coverage is 100%, and the schema already explains parameter behavior (auto-select, default). The tool description does not add new semantic value beyond the schema, so baseline 3 is appropriate.

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 'Resume a Contextium project from a session handoff' with specific actions: loads plan, finds last handoff note, briefs user. This distinguishes it from siblings like 'load_workflow' which may not include handoff context.

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?

Provides explicit example utterances for when to call ('resume my project', 'continue where I left off'), giving clear usage context. Does not mention when not to use or alternatives, so slightly below perfect.

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