Skip to main content
Glama

agentbay_memory_verify

Verify a memory entry is still accurate — resets confidence decay and increments helpful count. Also supports unhelpful marking and alias management.

Instructions

Verify a memory entry is still accurate — resets confidence decay and increments helpful count. Also supports unhelpful marking and alias management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
knowledgeIdYesMemory entry ID
actionYesAction to perform
aliasesNoSearch phrases to add (for add_aliases action)
phraseNoAlias to remove (for remove_alias action)

Implementation Reference

  • Handler function for the 'agentbay_memory_verify' tool. Calls PATCH /api/v1/projects/${projectId}/memory to verify (or unhelpful/alias-manage) a memory entry.
      async ({ projectId, knowledgeId, action, aliases, phrase }) => {
        const data = await apiPatch(`/api/v1/projects/${projectId}/memory`, { knowledgeId, action, aliases, phrase });
        if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
        return { content: [{ type: 'text' as const, text: `OK: ${data.action}${data.count ? ` (${data.count} aliases)` : ''}` }] };
      }
    );
  • Input schema for agentbay_memory_verify tool using Zod validation.
      projectId: z.string().describe('Project ID'),
      knowledgeId: z.string().describe('Memory entry ID'),
      action: z.enum(['verify', 'unhelpful', 'add_aliases', 'remove_alias']).describe('Action to perform'),
      aliases: z.array(z.string()).optional().describe('Search phrases to add (for add_aliases action)'),
      phrase: z.string().optional().describe('Alias to remove (for remove_alias action)'),
    },
  • src/index.ts:688-703 (registration)
    Registration of the 'agentbay_memory_verify' tool via server.tool() on the McpServer instance.
    server.tool(
      'agentbay_memory_verify',
      'Verify a memory entry is still accurate — resets confidence decay and increments helpful count. Also supports unhelpful marking and alias management.',
      {
        projectId: z.string().describe('Project ID'),
        knowledgeId: z.string().describe('Memory entry ID'),
        action: z.enum(['verify', 'unhelpful', 'add_aliases', 'remove_alias']).describe('Action to perform'),
        aliases: z.array(z.string()).optional().describe('Search phrases to add (for add_aliases action)'),
        phrase: z.string().optional().describe('Alias to remove (for remove_alias action)'),
      },
      async ({ projectId, knowledgeId, action, aliases, phrase }) => {
        const data = await apiPatch(`/api/v1/projects/${projectId}/memory`, { knowledgeId, action, aliases, phrase });
        if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
        return { content: [{ type: 'text' as const, text: `OK: ${data.action}${data.count ? ` (${data.count} aliases)` : ''}` }] };
      }
    );
Behavior3/5

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

With no annotations, the description must fully convey behavioral traits. It discloses core effects (confidence decay reset, helpful count increment) and additional actions (unhelpful marking, alias management). However, it omits details like whether actions are reversible, permission requirements, or rate limits, leaving gaps in transparency.

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 remarkably concise: two sentences with no filler. The first sentence captures the primary purpose, and the second lists additional capabilities. Every word is functional, and the structure is front-loaded.

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?

Given the tool's complexity (5 parameters, enum actions, no output schema), the description covers the main actions but lacks details on return values, error behavior, or side effects. It is minimally adequate for an experienced user but incomplete for a novice.

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 description coverage is 100%, so the schema already defines each parameter. The description adds context by grouping actions (verify, unhelpful, alias management) but does not provide new meaning beyond the enum values. Baseline 3 is appropriate as the description complements but does not significantly enhance parameter understanding.

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 tool verifies memory accuracy, resets confidence decay, and increments helpful count. It also mentions unhelpful marking and alias management, distinguishing it from other memory tools like store, recall, or forget. However, it does not explicitly differentiate from similar verification-focused siblings, leaving some ambiguity.

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, nor does it mention when not to use it. No usage context or exclusion criteria are given, forcing the agent to infer appropriate scenarios.

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/thomasjumper/agentbay-mcp'

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