Skip to main content
Glama
Sign In

cellmath

by studio.ai.cellmath
OverviewDiscussionsAdmin

session_handover

[PUBLIC READ] Generate a 4-tier continuity package [HMC + Organ + Cursor + Index + Cell] to transfer reasoning state ($S_t$) to a new agent or session without context explosion. Side effects: None (read-only).

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

Input Schema

NameRequiredDescriptionDefault
cursorNoCurrent active node ID pointer.
target_cell_idNoSpecific cell ID to inject in package.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Current active node ID."New value: +"Current active node ID pointer."
    • changedInput schema / properties / target_cell_id / description
      Previous value: -"Specific cell to inject in package."New value: +"Specific cell ID to inject in package."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose 'Side effects: None (read-only)' — meaningful safety context. However, it doesn't describe what the returned package actually contains, its size or token characteristics beyond the vague 'without context explosion', or what state is captured versus discarded.

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 sentences, front-loaded with the access tag and the core verb. The bracketed acronym chain is dense and unexplained, but the safety note at the end is well placed and nothing is redundant.

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?

For a two-optional-parameter, no-output-schema tool, the description covers purpose, safety, and the conceptual return shape. Remaining gaps are the undefined tier acronyms and how the two parameters interact, which keep it short of fully complete.

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%, so both optional parameters are already documented in structured data; the baseline is 3. The description adds no meaning about how cursor and target_cell_id affect the package contents or what happens when they are omitted.

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?

States a specific verb and resource ('Generate a 4-tier continuity package') plus its goal ('transfer reasoning state to a new agent or session'). The bracket list of tiers is undefined jargon, and it never names the sibling it differs from (session_status, causal_checkpoint, session_control), so an agent can't fully discriminate intent without inference.

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 handover use case ('to a new agent or session without context explosion') implies when to call it, but there is no explicit when-not guidance and no alternative routing among the many session/causal siblings. Usage is derivable rather than stated.

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

All cellmath toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources