Skip to main content
Glama

PCD (Portable Context Deck)

by ai.portablecontext.mcp
OverviewDiscussionsAdmin

Reground

reground
Read-only

Recover the active operating instructions when context has faded; read_topology refreshes work state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesYour CURRENT deck handle — reground re-projects the frame you already hold. To enter a different deck, use switch_deck instead.
contractNoHelp mode — return the complete contract with no operation performed.
sectionsNoTargeted slices to re-pull, e.g. ['own/guidelines','container/out_of_bounds','user','voice']. Layer wholes (own/container/company/user), 'layer/field' compounds, and asides (grounding/voice/orientation/precedence). Unknown slug → reject with available_sections.
projectionNofull (default) re-carries the whole frame; outline returns the layer/field map (counts + hashes, no bodies) for lean-then-fetch. Ignored when sections is set.
container_idNoContainer ID — required when user has multiple containers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / contract / description
      Previous value: -"Help mode — pass true to receive this tool's full _meta.contract (all variants) with NO operation performed."New value: +"Help mode — return the complete contract with no operation performed."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation covers the side-effect profile, and the description does not contradict it. However, the description adds no additional behavioral detail such as error cases, auth requirements, or state-change guarantees.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence. The read_topology clause adds useful orientation without bloat.

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?

No output schema is provided and the description only vaguely gestures at the result ('recover active operating instructions'). It does not specify what is returned or what the caller should expect after invocation.

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?

The input schema already documents all parameters with 100% coverage, so the baseline applies. The description proper adds no parameter-level information beyond what the schema already provides.

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 names a clear action ('Recover') and object ('active operating instructions'), with a trigger condition ('when context has faded'). It also references read_topology as a related sibling, though the precise boundary between the two is only lightly drawn.

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?

The description provides a condition for use ('when context has faded') and nods to an alternative ('read_topology refreshes work state'), but it does not explicitly state when to prefer this tool over the alternative or mention prerequisites.

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

All PCD (Portable Context Deck) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources