Skip to main content
Glama
GonzaloTorreras

ai-dememory

Unignore False Positive

memory.false_positive_unignore

Record a reviewed false positive unsuppression to update the ignore file, removing the suppression for a previously flagged item.

Instructions

Record a reviewed false-positive unsuppression in .ai-dememory-ignore.toml.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
reviewerYes
recommendation_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
pathYes
ignoredYes
reviewerNo
review_dueNo
reviewed_atNo
review_afterNo
recommendation_idNo
recommendation_pathNo
review_after_statusNo
recommendation_actionNo
canonical_memory_updatedYes
recommendation_policy_violationNo
Behavior3/5

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

Annotations indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it modifies a configuration file, which is useful but does not detail how (overwrite/append) or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but omits essential information. It could be expanded to cover parameter semantics without being overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters and an output schema, the description is insufficient. It fails to explain parameters or the expected output, leaving significant gaps for the agent.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the three parameters (id, reviewer, recommendation_id). The agent receives no guidance on what these parameters mean or how to use them.

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 clearly states the verb 'Record' and the resource 'reviewed false-positive unsuppression' along with the target file '.ai-dememory-ignore.toml'. However, the term 'unsuppression' may be unclear without context, and it doesn't fully differentiate from the sibling 'memory.false_positive_ignore'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'memory.false_positive_ignore' or 'memory.review_false_positives'. There is no mention of conditions for usage or exclusions.

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/GonzaloTorreras/ai-dememory'

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