Skip to main content
Glama
Sign In
memory-mcp

memory-mcp

by chenxiaofie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_reject_candidate

Reject a misjudged entity candidate from persistent memory to remove false associations and maintain accurate conversation history.

Instructions

拒绝一个误判的实体候选

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": {
      "candidate_id": "<candidate_id>"
    },
    "name": "memory_reject_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYes候选实体 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It only states 'reject' but does not disclose side effects (e.g., deletion, status change, reversibility) or any requirements. The behavioral impact is vague.

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?

A single sentence with no filler. Every word is necessary and directly conveys the tool's purpose.

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?

For a simple one-parameter tool with no output schema, the description is minimally adequate. However, given no annotations, it lacks behavioral context about the rejection process (e.g., what happens to the candidate).

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% with a single parameter described as '候选实体 ID'. The description adds no additional meaning beyond the schema. Baseline score is appropriate.

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 ('reject') and the resource ('entity candidate that was misjudged'). It distinguishes from siblings like memory_confirm_entity (which confirms a candidate) and memory_add_entity (which adds a new entity).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or any context for invocation.

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