Skip to main content
Glama

Detect No-op Action

detect_noop
Destructive

Determine whether an action attempt left state unchanged or matches a previous attempt, recording the result to detect repeat loops.

Instructions

Detect whether a tool call was a no-op (state unchanged) or identical to a prior attempt in the session — a cheap repeat-loop signal. Records the action attempt state for repeat detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionIdYesStable identifier for the action being checked (e.g. the file path or command being attempted)
kindNoAction kind: file edit/write or command execution
filePathNoPath of the file the action targets (file kind)
beforeContentNoFile content before the action (file kind)
afterContentNoFile content after the action (file kind)
exitCodeNoCommand exit code (command kind)
stdoutNoCommand stdout (command kind)
stderrNoCommand stderr (command kind)
sessionIdNoOptional session id used to scope repeat-attempt detection
Behavior3/5

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

Annotations include 'destructiveHint: true', but the description only mentions recording action state without clarifying side effects. The description adds context about recording state but lacks details on what modifications occur or if the tool is safe.

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?

The description is concise with two sentences, front-loading the core purpose and adding essential detail about state recording. No wasted words.

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?

The description explains the tool's purpose and that it records state, but does not describe return values (e.g., boolean or enum) or provide guidance on parameter differences ('file' vs 'command' kinds). Schema coverage mitigates but does not fully compensate.

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 the baseline is 3. The description adds minimal meaning beyond the schema, merely implying parameters define action state without explaining semantics or usage rules.

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?

The description clearly states the tool detects no-op actions or repeat attempts with a specific verb and resource. It differentiates from sibling tools like 'track_action' and 'record_action_receipt' by focusing on cheap repeat-loop detection.

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 description implies usage for detecting no-op or repeat actions and mentions 'cheap repeat-loop signal,' but does not explicitly specify when to use it over alternatives or provide when-not conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IgorGanapolsky/ThumbGate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server