Skip to main content
Glama

memory_proposal_status

Read-only

Check whether a Lucy memory proposal is pending, approved, rejected, expired, or superseded, and confirm that pending memory cannot be recalled until approved.

Instructions

Read whether a Lucy proposal is pending, approved, rejected, expired, or superseded. Pending memory is not recallable.

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": {
      "proposal_id": "<proposal_id>"
    },
    "name": "memory_proposal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
resultYes
statusYes
operationYes
relationsYes
requestedYes
created_atYes
decided_atYes
expires_atYes
schema_versionYes
proposal_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context by enumerating lifecycle outcomes and noting that pending memory is not recallable, but it says nothing about behavior for unknown or malformed proposal IDs (error vs. empty result) or whether status is immediately consistent.

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?

Two short sentences with no filler, and the core action is front-loaded before the caveat about pending memory. Every sentence carries information the agent can act on.

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?

The tool is simple (one required parameter), annotations cover the safety profile, and an output schema exists, so return values needn't be described. Still missing is what the agent should do with each state (e.g., retry on pending, resubmit on rejected) and how missing IDs are handled.

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?

Schema description coverage is 0% and the description never mentions the single parameter, proposal_id, so it adds no meaning beyond the schema's pattern constraint (^proposal_[A-Za-z0-9_-]+$). With only one required parameter the gap is small, but the description does not compensate for the missing coverage.

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 uses a specific verb and resource ("Read whether a Lucy proposal is...") and enumerates the full set of possible states, so an agent knows exactly what the call reports. It doesn't explicitly name how it differs from memory_propose or memory_recall, leaving sibling differentiation to inference.

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?

Usage is implied rather than stated: the agent can infer this is the follow-up check after submitting a proposal, and "Pending memory is not recallable" hints at why the check matters. There is no explicit when-to-use/when-not guidance and no reference to the sibling tools it complements.

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