Skip to main content
Glama
Sign In
resolve-mcp

resolve-mcp

by irstone-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clip_unlink

Unlinks clips from their source media, taking them offline while preserving their presence in the media pool.

Instructions

Take clips offline without removing them from the pool.

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": {
      "clip_handles": "<clip_handles>"
    },
    "name": "clip_unlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_handlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It discloses the core behavior (unlink, keep in pool) but omits details about reversibility, side effects, state dependencies, or error conditions.

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 description is concise at 10 words in a single sentence. However, it could add more value without becoming verbose. The structure is efficient but borderline under-specified.

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

Completeness2/5

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

Given no output schema, one undocumented parameter, and no annotations, the description is insufficient for reliable agent use. An agent lacks context on parameter format, expected outcomes, and operational constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the tool description does not explain the meaning of 'clip_handles' or how to obtain them. An agent cannot infer the parameter's purpose or format from the given information.

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 uses a specific verb-resource combination ('take clips offline') and clearly distinguishes from deletion by stating 'without removing them from the pool.' It contrasts well with sibling tools like clip_relink and clip_delete.

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?

No explicit guidance is provided on when to use this tool versus alternatives (e.g., clip_relink or clip_delete). The description only states the action without context about prerequisites or preferred scenarios.

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