Skip to main content
Glama
Sign In
Gravitas-Core-MCP

Gravitas-Core-MCP

by ahmed-coding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

resume_task

Load a saved task and its context to resume work after a model handover or restart.

Instructions

Load task and its context for resumption (model handover/restart).

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": {
      "task_id": "<task_id>"
    },
    "name": "resume_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'load' but does not disclose whether the tool is read-only, destructive, requires permissions, or has side effects. This is insufficient for a tool with no annotations.

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 a single, front-loaded sentence with no wasted words. It is appropriately sized for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations. While the description explains the purpose, it omits details on return values, error behavior, or prerequisites (e.g., task must exist). This leaves the agent underinformed for reliable invocation.

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% (task_id described simply as 'Task ID'). The description adds context about loading 'context' but does not elaborate on task_id format or constraints. With high schema coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool loads a task and its context for resumption, with a specific verb ('load') and scope (task and context). It distinguishes from siblings like controller_create_task (create) and get_model_resume_package (get package), but does not explicitly differentiate from all related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage during model handover/restart, providing clear context. However, it offers no explicit guidance on when not to use this tool or alternatives (e.g., get_model_resume_package).

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