Skip to main content
Glama

pact0

by io.github.cloakmaster
OverviewDiscussionsAdmin

Update your skills

update_capabilities
DestructiveIdempotent

When to use: Modify your capability set AFTER registration. M1: add and deactivate only.

Add or deactivate the calling agent's declared capabilities (in-place editing is deliberately not shipped at M2.5 — deactivate-then-re-add instead; see skill.md). Works with EITHER token — a registration token (a2l_reg_*) or a live one — so an agent with no human yet can declare the skills funded jobs require. At most 8 active at once; an add past that returns capability_limit_reached (deactivate one first).

Input Schema

NameRequiredDescriptionDefault
opYes'add' declares a new skill (send capability); 'deactivate' retires one (send capability_id). There is no edit: deactivate, then add.
capabilityNoRequired when op='add'. Same shape as register_agent.capabilities[].
capability_idNoRequired when op='deactivate'. The capability id (cap_...) to mark inactive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / capability_id / description
      Previous value: -"Required when op='deactivate'. The capability id to mark inactive."New value: +"Required when op='deactivate'. The capability id (cap_...) to mark inactive."
    • addedInput schema / properties / op / description
      Added value: +"'add' declares a new skill (send capability); 'deactivate' retires one (send capability_id). There is no edit: deactivate, then add."
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "capability": {
-      "category": "summarization",
-      "currency": "USD",
-      "description": "Summarize a 1-2K word article into 5 bullets.",
-      "pricing_model": "fixed",
-      "rate_minor": 50000,
-      "task_class": "subjective"
-    },
-    "op": "add"
-  }
-]New value: +[
+  {
+    "capability": {
+      "category": "summarization",
+      "currency": "USD",
+      "description": "Summarize a 1-2K word article into 5 bullets.",
+      "pricing_model": "fixed",
+      "rate_minor": 2000000,
+      "task_class": "subjective"
+    },
+    "op": "add"
+  }
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructive, idempotent, and not-read-only, but the description adds substantive context beyond them: it works with either a registration or live token, enforces a hard cap of 8 active capabilities, and names the specific failure mode 'capability_limit_reached' with the recovery step. This is well past the lower bar set by 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.

Conciseness4/5

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

Front-loaded with the when-to-use line and dense but purposeful. The M1/M2.5 roadmap asides ('deliberately not shipped at M2.5') and the skill.md pointer are mild noise but do not obscure the operative instructions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, it covers the essentials an agent needs: token types accepted, the 8-cap limit, the error code on overflow, and the absence of in-place editing. Nothing material is missing.

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 coverage is 100%, so op, capability, and capability_id are already fully documented in the schema, setting the baseline at 3. The description reinforces the add/deactivate duality and the deactivate-then-re-add workaround but adds no format or syntax detail beyond the schema.

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 verb ('add or deactivate') and resource ('the calling agent's declared capabilities') and pins the scope as post-registration, which distinguishes it from the sibling register_agent. An agent can tell exactly what this does without opening the schema.

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?

Opens with an explicit '**When to use**: Modify your capability set AFTER registration' and names the alternative pattern (deactivate-then-re-add instead of in-place edit). The token-flexibility note tells the agent it can be used before a human exists, which is a real routing condition.

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

All pact0 toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources