PLUR

Official

Overview Schema Source Related Servers Discussions Admin

plur_session_start

Read-only

Start a session to inject relevant engrams for your current task. Call this at the beginning of every session to load memory context for focused work.

Instructions

Start a session — inject relevant engrams for your task. Call at the beginning of every session.

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": {
      "task": "<task>"
    },
    "name": "plur_session_start"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Tags to filter injected engrams
`task`	Yes	What you are working on (triggers engram injection)
`default_scope`	No	Default scope for plur_learn calls this session when no explicit scope is provided. Only set this if you want ALL engrams to route to a specific store. Usually, leave unset and pass scope per-engram based on relevance.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0Jul 24, 2026

TDQS

B3.4/5.0

Behavior1/5

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

The description uses 'inject relevant engrams,' implying a write operation, but annotations declare readOnlyHint=true. This contradiction misleads about the tool's behavioral safety. Additionally, no other behavioral traits (e.g., side effects on persistent state) are disclosed.

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?

The description is concise at two sentences, with the purpose front-loaded. Every sentence is necessary and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a session-start tool with 3 parameters and no output schema, the description is too minimal. It lacks details on session lifecycle, idempotency (idempotentHint=false), and interaction with other tools like plur_inject. More context is needed for complete understanding.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 the tool's action ('Start a session — inject relevant engrams') and the resource ('session'). It distinguishes from siblings like plur_session_end by specifying it is for starting a session, called at the beginning.

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?

The description explicitly says 'Call at the beginning of every session,' providing clear when-to-use guidance. It does not mention exclusions or alternatives, but the context is well-defined by the sibling tool plur_session_end.

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