Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

resume_context

Read-only

Reads workspace notes, current plan, recent checkpoint, and Git status to restore context and resume work after a free-tier limit.

Instructions

Read notes, current plan, recent checkpoint and Git status to help resume after a free-tier limit.

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds value by listing the four data sources the agent will get back, but says nothing about output size, whether payloads are truncated, or what happens when a checkpoint or plan is absent — meaningful gaps for an aggregate reader.

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?

A single front-loaded sentence beginning with the verb 'Read', with no filler or redundant restatement of the name. Every clause (sources plus trigger) earns its place.

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?

With no output schema, the description carries the burden of describing returns and does so by naming the four fetched artifacts. It stops short of explaining formatting, ordering, or degraded cases such as a missing checkpoint, which would matter for an agent consuming this as its resume payload.

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

Parameters4/5

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

The tool takes no parameters and the description correctly presents it as a zero-argument call, so there is nothing to disambiguate. The baseline for a parameterless schema applies.

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 names a specific verb ('Read') and enumerates the exact resources it pulls in: notes, current plan, recent checkpoint and Git status. That makes the aggregate nature of the tool clear, distinguishing it from the individual readers like project_notes_read, plan_get, checkpoint_read and git_status, though it never explicitly states that it is a composite shortcut.

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?

It gives a concrete trigger — resuming work after a free-tier limit — which is enough for an agent to recognize the situation. It does not name alternatives or say when to call the individual readers instead, so the guidance is clear but not exhaustive.

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