Skip to main content
Glama

body_skill_replay

Replays a verified skill's recorded steps in order with the same targets, content, permission gate, and verification; refuses unverified skills until they are checked.

Instructions

Do exactly the same thing again: replay a verified skill's steps, in order.

Same targets, same content, same permission gate, same verification - this is the 'copy paste the same' path. Unverified skills are refused until someone checks them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_id": "<skill_id>"
    },
    "name": "body_skill_replay"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
skill_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the same permission gate and verification apply and that unverified skills are rejected, but says nothing about failure modes, what happens if the target changed, or whether re-running is idempotent.

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 short sentences, front-loaded with the core action and followed by the scope qualifiers and the eligibility gate. No filler, though the quoted 'copy paste the same' aside is slightly colloquial.

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?

No output schema or annotations, and parameter documentation is absent at both the schema and description level, so an agent lacks enough to invoke it confidently beyond a bare skill_id. The behavioral picture is partially covered by the verification and permission-gate statements.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, and the description adds no meaning for skill_id (required) or task_id (optional). A calling agent must guess the identifier semantics and what task_id does from the names alone.

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: replay a verified skill's steps, in order, with identical targets, content, permission gate and verification. It is clearly distinguishable from save/list siblings by the 'replay' framing, though no sibling is named.

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?

Gives clear usage context ('Do exactly the same thing again', the 'copy paste the same' path) and an explicit precondition that unverified skills are refused until checked. It stops short of naming an alternative for first-time or modified runs.

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