Skip to main content
Glama
Sign In
PLUR

PLUR

Official
by plur-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plur_packs_preview

Read-onlyIdempotent

Review a pack before installing it—see its manifest, engram list, security scan, and warnings to make an informed decision.

Instructions

Preview a pack before installing — shows manifest, engram list, security scan, and warnings. Always call this before plur_packs_install to let the user review what they are importing.

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": {
      "source": "<source>"
    },
    "name": "plur_packs_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesPath to the pack directory to preview

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and description reinforces read-only preview nature, adding detail on what is shown. No contradictions.

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 sentences, no wasted words. Information is front-loaded and to the point.

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

Completeness5/5

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

Given simple tool structure (1 param, no output schema), description fully covers purpose, behavior, and usage. Annotations fill the rest.

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

Parameters4/5

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

Single parameter 'source' is well-described in schema with 100% coverage. Description implicitly confirms its use without adding syntax details, which is adequate.

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 'Preview a pack before installing' and lists specific outputs (manifest, engram list, security scan, warnings). Distinguishes from sibling plur_packs_install.

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?

Explicitly says 'Always call this before plur_packs_install' providing clear when-to-use guidance. Could mention when not to use but still strong.

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