Skip to main content
Glama

PCD (Portable Context Deck)

by ai.portablecontext.mcp
OverviewDiscussionsAdmin

Create Deck

create_deck

Create a deck from its applicable template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the deck — unique per account.
handleYesLoad handle — lowercase, hyphens, max 24 chars, unique per account.
contractNoHelp mode — return the complete contract with no operation performed.
customiseNoDot-path overrides applied to the template — e.g. { "deck.content.intent": "..." }
deck_typeYesDeck type — closed 3-type set. Bootable: container-context, specialized-context. Passive: container-meta (the specialist roster). user-meta and company-meta are account configuration, not decks — use update_meta.
container_idNoContainer ID to associate the deck with
template_slugNoTemplate slug — defaults to pcd-system-doc-schema-{deck_type}-json

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / deck_type / description
      Previous value: -"Deck type — closed 5-type set. Bootable: container-context, specialized-context. Passive: container-meta, user-meta, company-meta."New value: +"Deck type — closed 3-type set. Bootable: container-context, specialized-context. Passive: container-meta (the specialist roster). user-meta and company-meta are account configuration, not decks — use update_meta."
    • changedInput schema / properties / deck_type / enum
      Previous value: -[
-  "container-context",
-  "specialized-context",
-  "container-meta",
-  "user-meta",
-  "company-meta"
-]New value: +[
+  "container-context",
+  "specialized-context",
+  "container-meta"
+]
  2. 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."
  3. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds only the vague 'from its applicable template' and omits what actually happens on creation, whether a template is required or auto-selected, and any side effects. It adds little beyond the annotations.

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

Conciseness3/5

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

It is a single short sentence with no waste, but the terseness reflects under-specification rather than disciplined concision. It is appropriately front-loaded but too thin for a 7-parameter creation tool.

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 7-parameter mutation tool with nested objects, an enum, and no output schema, the description is far too sparse. It says nothing about the required fields, the special 'contract' help mode, the deck_type set, or the template default, all of which the agent must discover from the schema alone.

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 fully documents name, handle, deck_type, contract, customise, container_id, and template_slug. The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (create a deck) and adds that it derives from a template, which is more than a bare restatement of the name. However, 'its applicable template' is circular and it does nothing to distinguish this tool from siblings like create_container or create_pcd_skill. Adequate but with clear gaps.

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

Usage Guidelines2/5

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

No guidance is given on when to create a deck versus using load_deck, switch_deck, or update_deck, nor are prerequisites (e.g. needing a container) mentioned. The agent is left to infer usage entirely from the name.

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