Skip to main content
Glama
Sign In
splicedeck

splicedeck

by ihuzaifashoukat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

colour

Select and apply a color treatment to a video cut sheet, and optionally insert a transfer stage, by specifying the target color range and look.

Instructions

Decide the colour treatment for a cut sheet, including whether a transfer stage is inserted.

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": {
      "sheet": "<sheet>"
    },
    "name": "colour"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoIdempotency key.
lookNoA look slot name declared in the party's kit. Null uses the settled finding.
sheetYesA cut sheet handle.
target_rangeNosdr, hlg, or pq.sdr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects and safety profile, but it only states that it decides colour treatment without indicating whether it modifies the cut sheet, requires permissions, or what the output is. The phrase 'including whether a transfer stage is inserted' hints at a possible mutation but is ambiguous.

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 a single sentence that immediately states the verb and object, with no wasted words. However, it is under-specified, which is a completeness issue rather than a conciseness issue.

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?

The tool has four parameters with an enum and no output schema, requiring the description to explain return values and effects. The description does not cover what happens after the decision, what a 'transfer stage' is, or what the caller should expect, making the tool under-explained.

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?

All four parameters have schema descriptions (100% coverage), so the description itself adds no additional meaning to the parameters. The term 'cut sheet' aligns with the `sheet` parameter, but no deeper semantics are provided 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?

The description uses the specific verb 'Decide' with the resource 'cut sheet' and mentions a key aspect (transfer stage insertion), making its function clear and distinct from sibling tools like apply or preview.

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 usage guidance is provided; the description does not mention when to use this tool over alternatives or any prerequisites/exclusions.

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