Skip to main content
Glama

ctxstore — memory that follows you across models

Resume Session

resume_session
Read-onlyIdempotent

Call to load session continuity. Last session: no prior session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and repeatability profile is covered. The description contributes the current state ('no prior session'), which hints that the returned content is conditional on prior-session existence, but it never says what continuity data is returned or what happens on a first run. With annotations doing the heavy lifting, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two very short sentences, no padding, and the action verb is front-loaded. The second sentence is a dynamic state note rather than filler, though it is of limited help for deciding how to call the tool.

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

Completeness3/5

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

For a zero-param read with rich annotations and no output schema, the main open question is what 'session continuity' actually returns, and the description only says there is no prior session. It is adequate to invoke but leaves the agent guessing about the payload and about its relationship to the other session/context tools.

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 zero parameters and the schema explicitly forbids additional properties, so there is nothing for the description to disambiguate. Baseline 4 for a no-parameter tool.

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

Purpose3/5

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

States a verb ('load') and a resource ('session continuity'), so the general intent is legible, but 'session continuity' is an internal concept that is never defined, and the description does not distinguish itself from siblings such as get_session_seed, load_context, or wake_status. The appended dynamic line 'Last session: no prior session' adds state but not purpose.

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?

'Call to load session continuity' weakly implies this is a start-of-session bootstrap step, but there is no explicit when-to-use statement, no when-not-to-use, and no routing to the clearly related siblings (get_session_seed, load_context, wake_status). The agent must infer the trigger condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.