Skip to main content
Glama
Sign In
Baton

Baton

by timurabi3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

baton_status

Check for existing handoff state in a project and retrieve a one-glance summary at session start to resume work across sessions.

Instructions

Check if a baton (handoff state) exists for this project and get a one-glance summary. Call this at session start.

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

Input Schema

NameRequiredDescriptionDefault
projectNoProject root path (default: cwd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Check' and 'get a one-glance summary' imply a read-only operation, but the description does not explicitly state that it has no side effects or describe what the summary contains.

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 short sentences, no filler, and the key action and timing are front-loaded. Every sentence contributes behavioral or usage guidance.

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 simple optional-parameter status check, the description provides the essential purpose, timing, and output shape. The only minor omission is a more concrete indication of what the summary includes, but that does not block correct 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?

The only parameter is project, and schema coverage is 100%; the description adds no parameter-level detail beyond that, which is acceptable given the baseline for full schema coverage.

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 action (check existence) and resource (baton/handoff state) plus the deliverable (one-glance summary). It reads clearly as a status/read sibling to the action-oriented baton tools, though it does not explicitly contrast with baton_history.

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?

Explicitly instructs 'Call this at session start,' giving the agent a clear trigger condition. It does not list exclusions or alternatives, but the sibling names make the intended role evident.

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