Skip to main content
Glama

PCD (Portable Context Deck)

by ai.portablecontext.mcp
OverviewDiscussionsAdmin

Create PCD Skill

create_pcd_skill

Create a reusable working method when the user wants a procedure preserved for future use. Use update_pcd_skill to revise an existing method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSkill name — lowercase, underscores/hyphens, max 48 chars. Unique per deck; if shared, unique across the container.
actionNoDefault 'write'. 'validate': pre-send check — name format/cap (48), description shape, signal_emission — WITHOUT writing; returns { valid, missing_required[], over_cap: [{field, len, cap}], not_checked? }. Uniqueness, deck resolution and the skill allowance still run at write time (not_checked names them).
sharedNoIf true, skill is visible to vertical neighbours at boot. Container-context shared → specialized-contexts inherit. Specialized-context shared → container-context inherits. Default false.
contractNoHelp mode — return the complete contract with no operation performed.
deck_handleYesHandle of the deck this skill belongs to — must be a container-context or specialized-context deck
descriptionYesStructured metadata for indexing and LLM dispatch
container_idYesContainer ID
raw_markdownNoFull instruction body the LLM reads when the skill is invoked. May reference declared resources via {{ref:Name}} syntax. Omit to create a stub.
signal_emissionNoOptional. Declares the signal this skill emits. The client AI fires write_signal at the declared point — run_pcd_skill surfaces it as an explicit emit_contract; the worker never auto-fires.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"Default 'write'. 'validate': pre-send check — name format/cap (48), description shape, signal_emission — WITHOUT writing; returns { valid, missing_required[], over_cap: [{field, len, cap}], not_checked? }. Uniqueness and deck resolution still run at write time."New value: +"Default 'write'. 'validate': pre-send check — name format/cap (48), description shape, signal_emission — WITHOUT writing; returns { valid, missing_required[], over_cap: [{field, len, cap}], not_checked? }. Uniqueness, deck resolution and the skill allowance still run at write time (not_checked names them)."
  2. Changed1 schema field changed
    • changedInput schema / properties / description / properties / triggers / description
      Previous value: -"PCD tool names this skill is relevant AFTER, e.g. [\"write_knowledge\"]. When a declared tool runs in this container, its response carries a one-line _meta.skill_hint naming this skill — so encoded method surfaces at the moment of use instead of being improvised past. Exact tool-name equality, no prose matching: when_to_use stays the human/AI-facing half, triggers is the mechanical half. Advisory only — never blocks, never auto-runs, fires once per skill in normal operation. Omit for no nudge (the default)."New value: +"PCD tool names this skill is relevant AFTER, e.g. [\"write_knowledge\"]. When a declared tool runs in this container, its response carries a one-line _meta.skill_hint naming this skill — so encoded method surfaces at the moment of use instead of being improvised past. Explicit operation identities preserve legacy declarations; consolidated umbrella names match their operation family. No prose matching: when_to_use stays the human/AI-facing half, triggers is the mechanical half. Advisory only — never blocks, never auto-runs, fires once per skill in normal operation. Omit for no nudge (the default)."
  3. Changed3 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."
    • addedInput schema / properties / description / properties / status
      Added value: +{
+  "description": "Omit for active. Retired skills are hidden from discovery and hints; named reads return reference-only retirement guidance. Versioned with the description.",
+  "enum": [
+    "active",
+    "retired"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the basic mutation profile is already covered and the description is consistent with it. However, the description adds almost no behavioral context of its own — no mention of uniqueness/collision handling, shared visibility effects, or the validate/contract help modes that the schema documents. With annotations carrying the safety profile, a 3 reflects a description that adds little beyond them.

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, front-loaded with the action and followed immediately by the alternative. No filler, no repetition of schema content.

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?

For a nine-parameter mutation with nested objects and no output schema, the rich schema covers argument meaning but the description says nothing about the return value (e.g., created skill identity/handle) or the validate/contract modes. The schema compensates for most of the parameter burden, leaving the description minimally adequate rather than complete.

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% and nine parameters (including nested objects, enums, and detailed per-field docs for action, shared, triggers, data_refs, signal_emission) are all fully specified in the schema. The description contributes no parameter detail, so the baseline 3 is correct when the schema does all the heavy lifting.

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 gives a specific verb ('Create') and glosses the resource as 'a reusable working method ... a procedure preserved for future use,' so the agent knows it writes a persistent skill rather than invoking one. It explicitly names the sibling update_pcd_skill, distinguishing create from revise. It stops short of 5 only because the domain term 'PCD Skill' is left as-is without tying it to other create_* siblings.

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?

It states a clear trigger ('when the user wants a procedure preserved for future use') and routes revisions to update_pcd_skill, which is genuine alternative guidance. It doesn't state exclusions or when to prefer list_pcd_skills/run_pcd_skill, so it lacks the explicit when-not coverage that a 5 requires.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources