Skip to main content
Glama

show_behavior

Runs a command on both the previous and current code, then shows the real outputs side by side so reviewers can verify what a change does.

Instructions

Show reviewers what a change does. grasp runs your command twice, on the code from before this session and on the code now, and shows both real outputs side by side. The command runs from the project root with sh; it must start and stop anything it needs and print a short result. Use one call per behavior you want to demonstrate.

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": {
      "title": "<title>",
      "command": "<command>"
    },
    "name": "show_behavior"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYeswhat the example shows, at most 8 words, e.g. Empty title is rejected
expectNowhat the new code should print, in plain words
commandYesshell command run from the project root; print one short line per case, like: empty title -> 400 title is required; start and stop anything it needs, e.g. a server, within the command
decisionNotitle of the decision this example demonstrates

Output Schema

NameRequiredDescriptionDefault
resultYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the command runs twice (before/after), executes from the project root via sh, must be self-contained (start and stop anything it needs), and must print a short result. It omits failure handling, timeouts, and side-effect safety, which keeps it from a 5.

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?

Four sentences, front-loaded with the purpose before the mechanism and constraints. Each sentence contributes, though the mechanism explanation is slightly verbose.

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?

An output schema exists, so return values needn't be explained, and the description covers mechanism, execution environment, and self-containment. It stops short of covering failure modes or runtime limits for a command-executing tool.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the command runs from the project root with sh, must be self-contained, and should print one short line per case. This clarifies the command parameter's expected shape beyond the schema text.

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

Purpose5/5

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

States a specific verb and resource ('Show reviewers what a change does') and immediately explains the mechanism: grasp runs the command twice, on pre-session and current code, and shows both outputs side by side. An agent can distinguish this from get_review_feedback and record_decision without opening any schema.

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?

'Use one call per behavior you want to demonstrate' gives clear granularity guidance for invocation. It does not name alternatives or state when-not to use it, but the usage context is unambiguous.

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