Skip to main content
Glama

edb_remove_comment

DestructiveIdempotent

Remove a previously added comment from a specified memory address. Helps maintain clean debug annotations.

Instructions

Remove an annotation previously added with edb_add_comment.

Args: params (AddressOnlyInput): Address - address (str): Address to remove comment from

Returns: str: Confirmation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Description mentions 'Remove' matching destructiveHint, and returns confirmation string. It adds that it works on previously added comments but does not discuss error cases or idempotency.

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?

Short and front-loaded, but includes redundant docstring format (Args/Returns) that repeats schema. Could be slightly more concise.

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?

Given simple tool with annotations and output schema, description covers essential use case. Missing details on error handling but sufficient for basic use.

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?

Description repeats schema parameter info without adding significant new meaning beyond 'Address to remove comment from'. No explanation of validation or behavior.

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 action (remove) and resource (annotation), and references the sibling tool edb_add_comment. It is distinct from other tools like edb_list_comments.

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?

States the tool is for removing annotations added by edb_add_comment, but lacks explicit guidance on when to use or not use it, and no alternatives mentioned.

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/oakkaya/edb-debugger-mcp'

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