Skip to main content
Glama

Confirm a record

padam_confirm

Confirm that a retrieved memory is still correct, refreshing its record and slightly raising confidence so repeated retrieval alone cannot keep wrong memories fresh.

Instructions

Mark a retrieved record as still true. Call this when a memory you used turned out to be correct. This refreshes the record and raises its confidence a little each time. Retrieval alone does NOT confirm a record: a wrong memory that gets retrieved often would otherwise stay forever fresh.

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": {
      "id": "<id>"
    },
    "name": "padam_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord id, as returned by padam_search or padam_write

Output Schema

NameRequiredDescriptionDefault
idYes
confirmedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "confirmed": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "confirmed"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.4.8

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds real value on top: it names what changes (freshness and confidence), that the effect is cumulative ("a little each time"), and explains why the operation is non-idempotent. It stops short of stating whether repeated confirms can ever be harmful or capped.

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?

Three tight sentences: action first, trigger condition second, and the important caveat about retrieval last. No filler, no restatement of the name or title.

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?

For a one-parameter mutation with an output schema, the description covers trigger, effect, and cumulative semantics well enough to call it correctly. Only the relationship to padam_refute and any confidence cap are left unstated.

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% and the single `id` parameter already documents its source (padam_search or padam_write) and length bounds. The description adds nothing about the id beyond what the schema says, so the baseline 3 applies.

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?

"Mark a retrieved record as still true" gives a specific verb (mark/confirm) and resource (a retrieved record), plus the effect (refresh + confidence bump). It implicitly sets itself apart from padam_refute by framing confirmation as the positive counterpart, though it never names that sibling.

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

Usage Guidelines4/5

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

"Call this when a memory you used turned out to be correct" is an explicit trigger condition, and the closing sentence supplies an explicit when-not: retrieval alone does not confirm. What's missing is a pointer to padam_refute for the opposite case, which would make routing unambiguous.

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