Skip to main content
Glama

PCD (Portable Context Deck)

by ai.portablecontext.mcp
OverviewDiscussionsAdmin

Get Signals

get_signals
Read-only

Inspect deferred conditions and their progress. Use for outstanding findings; read_topology holds current work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoScope the read to specific signal ids (e.g. picked from a titles scan) — container-guarded; unknown or cross-container ids are rejected with missing_ids, never a silent partial. When present, status defaults to 'all' so a just-resolved pick still reads.
handleYesDeck handle — used to resolve the container
statusNoFilter by signal status — defaults to 'open' ('all' when ids are passed). 'all' returns every status.
contractNoHelp mode — return the complete contract with no operation performed.
projectionNoResponse grain — default 'full'. 'count' → { total, open, by_severity, by_assigned }: the cheapest triage headline. 'titles' → enriched triage rows { id, severity, title, assigned_to, signal_type, occurrence_count } — self-sufficient for a severity/owner table, no content. 'full' → the complete v2 payload incl. content + the updates[] ring. Lean-then-fetch: titles scan → pick ids → projection='full' with ids.
assigned_toNoFilter to signals routed to one deck handle — the routed read for deck-scoped surfaces. Omit for the full container queue.

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

A4.2/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile, lowering the bar. The description adds context that signals are deferred/outstanding conditions, but it does not describe response shape or edge cases; no contradiction with annotations.

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 short sentences with no filler. The core action is front-loaded, and the sibling-routing clause earns its place by preventing a wrong tool choice.

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?

Given the detailed schema and read-only annotations, the definition is nearly complete: it supplies the business context that structured fields cannot. The only minor gap is that the description itself does not summarize the returned payload, though the projection parameter effectively fills this in.

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?

Parameter descriptions in the input schema cover 100% of the parameters and are unusually rich (e.g. ids container-guarding, projection grain, status defaults). The tool description itself adds no parameter-level meaning, so the baseline of 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?

States a specific action ('Inspect') and a specific resource ('deferred conditions and their progress'), immediately clarifying what signals are. It also distinguishes from the sibling read_topology by saying that tool 'holds current work'.

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 recommends this tool for 'outstanding findings' and points to read_topology for current work, giving both a when-to-use and a when-not-to-use signal. This is sufficient routing even without opening the schema.

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