Skip to main content
Glama
Sign In
PLUR

PLUR

Official
by plur-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plur_promote

Idempotent

Promote candidate engrams to active status so they appear in injection results. Use when your agent's memory candidates need to be activated.

Instructions

Activate candidate engrams so they appear in injection results

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plur_promote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSingle engram ID to promote
idsNoMultiple engram IDs to promote

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds that it activates engrams to appear in injection results, which is consistent and provides some behavioral context, but no additional details about side effects or state changes are given.

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, concise sentence that communicates the core functionality without unnecessary words or structure.

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 tool with no output schema and annotations, the description provides minimal but adequate context. Missing details like what 'candidate' means or idempotent behavior, but annotations compensate partially.

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 descriptions for both parameters ('Single engram ID to promote' and 'Multiple engram IDs to promote'). The tool description does not add further meaning beyond the schema.

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 'Activate' and the resource 'candidate engrams' with a specific outcome 'appear in injection results'. It vaguely distinguishes from siblings like plur_inject but does not explicitly differentiate from similar tools like plur_pin.

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 on when to use this tool versus alternatives (e.g., plur_inject, plur_pin). The description does not mention prerequisites, conditions, or excluded use cases.

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