Skip to main content
Glama
Sign In
PLUR

PLUR

Official
by plur-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plur_suggest_scope

Read-onlyIdempotent

Score an engram's statement, domain, and tags against scope covers to suggest matching registered scopes. Returns ranked candidates; advisory only.

Instructions

Suggest which registered scope(s) an engram belongs in, ranked by fit. Deterministic — no LLM, no network. Scores the statement keywords, optional domain (a dotted namespace like "plur.core.security"), and tags against the covers[] each scope declares. ADVISORY ONLY: this does not route or store anything; pass the chosen scope to plur_learn yourself. Returns candidates sorted by confidence (empty when nothing matches).

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": {
      "statement": "<statement>"
    },
    "name": "plur_suggest_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tags on the engram
domainNoOptional dotted namespace for the engram (e.g. "plur.core.security") — strongest routing signal
statementYesThe engram statement to route

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint; description reinforces determinism and no side effects, expands with 'no LLM, no network' and advisory nature. No contradiction.

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?

Four concise sentences, each adding value: purpose, determinism, advisory note, return format. Front-loaded with main purpose.

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?

Explains input usage, behavior, and output format. Lacks detailed candidate structure but sufficient given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, description adds meaning by explaining how parameters are scored (keywords, domain, tags) and that domain is strongest signal, beyond schema descriptions.

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?

The description clearly states it suggests scopes for an engram ranked by fit, distinguishes from routing tools by stating it's advisory only, and differentiates from siblings like plur_learn.

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

Usage Guidelines5/5

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

Explicitly says when to use (to determine scope), what it does not do (route or store), and directs to plur_learn for actual storage. Also explains return expectations (empty when nothing matches).

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