Skip to main content
Glama
Sign In
PLUR

PLUR

Official
by plur-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plur_meta_engrams

Read-onlyIdempotent

List META-prefixed engrams with structural templates and confidence scores. Filter by domain, hierarchy level, or confidence to verify and correct AI agent memory.

Instructions

List existing meta-engrams (engrams with META- prefix) with their structural templates and confidence scores

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_meta_engrams"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 20)
domainNoFilter by domain prefix (e.g. meta, meta.trading)
min_confidenceNoMinimum composite confidence score (0-1)
hierarchy_levelNoFilter by hierarchy level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint; description adds that it returns templates and confidence scores, but doesn't disclose additional behavioral traits beyond what annotations and schema imply.

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?

Single sentence with no redundant words; clearly conveys purpose and what is returned.

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?

With no output schema, the description adequately explains return content (structural templates, confidence scores). All 4 optional parameters are described in schema; the description implies filtering but lacks explicit statements about ordering or pagination.

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%, so each parameter has a description. The tool description does not add additional meaning beyond the schema, baseline 3 applies.

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?

Description clearly states the tool lists meta-engrams with specific properties (structural templates, confidence scores), distinguishing it from other tools like plur_extract_meta and plur_validate_meta that perform different operations.

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?

No explicit guidance on when to use this tool vs alternatives; usage is implied by the description but no when-not-to-use or alternative naming.

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