Skip to main content
Glama

handoff_capabilities

Read-only

Reads handoff.md to report what the agent may do alone, must ask first, and must never do. Flags missing sections and unedited template placeholders.

Instructions

What the user's handoff.md says the agent may do alone, must ask first, and must never do. Sections that are missing or empty are listed under unreadable, never guessed. unedited: true means the file still has template placeholders, so tell the user to fill it in before relying on it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. Beyond that, the description discloses two non-obvious behaviors: missing or empty sections are surfaced under `unreadable` rather than inferred, and `unedited: true` flags placeholder template content. These are trust-relevant semantics the schema does not carry.

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?

Three sentences, each doing distinct work: what is returned, how gaps are handled, and how to interpret the unedited flag. It is somewhat dense with backticked field names, but nothing is filler and the content is front-loaded.

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 explaining return semantics, and it covers the two non-obvious result fields (`unreadable`, `unedited`) plus the refusal-to-guess guarantee. The three permission tiers are described conceptually but their exact field names and shapes are not enumerated, leaving a small gap.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on return-value semantics, which is the right allocation.

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 the specific artifact (handoff.md) and the specific content returned: three permission tiers (may do alone / must ask first / must never do). An agent can tell this is a read of the user's declared agent rules, distinct from message-oriented siblings like handoff_read or handoff_inbox. It never states the verb 'reads' explicitly, relying on 'says the agent may do' to imply it.

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?

Usage is only implied: an agent should consult this before acting autonomously, and the description adds a concrete directive to tell the user to fill in the file when `unedited: true`. There is no explicit statement of when to call this versus other handoff tools, and no stated prerequisite for calling it.

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