Skip to main content
Glama

PCD (Portable Context Deck)

by ai.portablecontext.mcp
OverviewDiscussionsAdmin

Connection Call

connection_call
Destructive

Execute one or several independent external actions using discovered schemas. Returns a result for each call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsYesUp to 10 logically-independent calls. Order is preserved in the response.
contractNoHelp mode — return the complete contract with no operation performed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / action
      Removed value: -{
-  "description": "Action id returned by connection_browse, e.g. 'linear.list_linear_teams'.",
-  "type": "string"
-}
    • removedInput schema / properties / args
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Arguments object matching the action's input_schema.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
    • addedInput schema / properties / calls
      Added value: +{
+  "description": "Up to 10 logically-independent calls. Order is preserved in the response.",
+  "items": {
+    "properties": {
+      "action": {
+        "description": "Action id, e.g. 'linear.update_issue'.",
+        "type": "string"
+      },
+      "args": {
+        "additionalProperties": {},
+        "description": "Arguments object matching the action's input_schema.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • 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."
    • changedInput schema / required
      Previous value: -[
-  "action"
-]New value: +[
+  "calls"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate non-readonly and destructive potential, and the description adds that actions are independent and produce per-call results. However, it does not explain side effects, error behavior, or that calls may have lasting external impact beyond the annotation hints.

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?

The description is compact and front-loaded, and each parameter has a concise, informative description. There is no redundant or extraneous text.

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?

With no output schema and only a one-line description, important context is missing regarding response format, error handling, and how discovered schemas are provided. The contract mode partially mitigates this, but the tool would benefit from more operational context.

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?

All parameters have clear schema descriptions: calls, action, args, and contract. The contract help-mode parameter is well explained, and the args object appropriately references the action's input schema. The dynamic nature of args limits deeper semantic detail, but the coverage is strong.

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 clearly states that the tool executes one or more independent external actions using discovered schemas and returns a result per call. It distinguishes this as a generic dispatching tool, though it could more explicitly contrast with the many sibling tools.

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?

There is no explicit guidance on when to use this tool versus the sibling tools, nor any mention of prerequisites like needing discovered schemas or connection credentials. The phrase 'using discovered schemas' hints at context, but it does not provide concrete usage direction.

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