Skip to main content
Glama

skein_resume_delegated

Idempotent

Undo skein_drop_delegated — bring this issue back to your Delegated tab. Removes your user id from the issue's dismissed_by array so the Delegated predicate stops filtering it out. ANSWERS WITH AN ACKNOWLEDGEMENT by default — the id, the applied state and the new version, no issue card and no prose — so the expectedVersion cycle continues without a re-read; pass verbose for the full IssueDetail.

Does NOT re-arm bell notifications: the unsubscribe done by skein_drop_delegated (and its opt-out, when one was recorded) stays in effect until you call skein_watchers(action="watch") separately. Two distinct intents — Delegated lens visibility vs bell-notification flow — and resume only restores the first.

Idempotent: calling on an issue you haven't dropped is a silent no-op. The acknowledgement carries dismissed — YOUR membership in dismissed_by after the call (false here) — because neither status nor version moves, so it is the only proof the write applied.

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": {
      "id": "<id>"
    },
    "name": "skein_resume_delegated"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHierarchical issue id, e.g. demo-42 or sk-14.
verboseNoReturn the full IssueDetail, prose included. Default false = acknowledgement: `id`, `ok`, `version` plus the post-state stamps that apply (`status`, `assignee`, lock / claim / close stamps) — no issue card and no free text. The version is always there, so the expectedVersion cycle needs no extra read. Details: skein_get_instructions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotency, and non-destructiveness, and the description still adds meaningful behavior: the default acknowledgement payload (id, ok, version, post-state stamps), the verbose alternative, and the fact that the dismissed stamp is the only proof the write applied. It also discloses the no-op path on an issue not dropped.

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?

The opening sentence carries the purpose and is front-loaded, followed by the mechanism, return shape, and caveat in a logical order. The closing explanation of the `dismissed` stamp is useful but sits apart from the response-format paragraph, so it is slightly redundant.

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?

There is no output schema, and the description compensates by describing the acknowledgement fields, the verbose variant, and the idempotency edge case. Nothing needed to call this correctly for its two parameters is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the reason `verbose` exists (the expectedVersion cycle continues without a re-read) rather than just restating the schema. The `id` parameter gets no extra meaning, which keeps this short of a 5.

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?

The description states a specific verb and resource ('Undo skein_drop_delegated — bring this issue back to your Delegated tab') and names the exact mechanism ('Removes your user id from the issue's dismissed_by array'). An agent can tell it apart from the sibling drop tool without opening either 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?

It names the inverse operation explicitly and routes the agent onward for the adjacent-but-different intent: bell notifications require skein_watchers(action="watch") separately. It also states what selecting this intent does not accomplish, and describes the no-op case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.