Skip to main content
Glama
Sign In
SuperSkill

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

session

DestructiveIdempotent

Register, update, or query active agent sessions for multi-agent coordination. On complete, persists a session note to the vault.

Instructions

Register, update, or query active agent sessions for multi-agent coordination. On complete, persists a session note to the vault.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "session"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoTool name: claude-code|opencode|codex
actionYesSession action
blockedNoBlocking issues (for complete)
outcomeNoSession outcome (for complete)
projectNoProject being worked on
completedNoCompleted work items (for complete)
session_idNoSession ID (for heartbeat/complete)
allow_sharedNoAllow registering in a workspace already claimed by another active session
task_summaryNoWhat this session is doing
files_touchedNoFiles this session modifies
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.
tasks_completedNoTask IDs completed (for complete)
verification_runNoVerification steps run and results (for complete)
commands_to_resumeNoCommands to resume work (for complete)
partially_completedNoPartially completed work items (for complete)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.0
    • addedInput schema / properties / allow_shared
      Added value: +{
+  "description": "Allow registering in a workspace already claimed by another active session",
+  "type": "boolean"
+}
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is largely covered. The description adds one useful side-effect detail ('On complete, persists a session note to the vault') but omits the concurrency/workspace-claim behavior implied by the allow_shared and workspace_path parameters, which is the key coordination trait.

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 tight sentences, front-loaded with the verbs and scope, followed by the one side-effect worth calling out. Zero waste and no filler.

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 15-parameter, multi-action tool with no output schema, the description is thin: it never maps params to the register/heartbeat/complete/list_active actions (and its verb 'update'/'query' do not even match the enum names). It is minimally viable given the strong schema coverage but leaves the action-parameter contract to inference.

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% across all 15 parameters, so the schema carries semantics. The description adds only generic context ('On complete, persists...') and does not map the four action enum values to their relevant parameters, so baseline 3 is correct.

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 names specific verbs (register, update, query) and the resource (active agent sessions) plus the domain (multi-agent coordination), so the tool's purpose is clear. However, it does not differentiate itself from the sibling tool 'register', which invites confusion about which to call.

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

Usage Guidelines3/5

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

'For multi-agent coordination' implies the context of use and the sentence about persisting on 'complete' hints at workflow placement. But there is no explicit when-to-use versus the sibling 'register' tool, no prerequisites, and no when-not conditions.

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

Deploy Server

Other Tools