Skip to main content
Glama

filter_set

Adjust a video’s brightness, contrast, saturation, gamma, or hue by setting the chosen filter to a value from -100 to 100.

Instructions

Set a video filter (brightness | contrast | saturation | gamma | hue) to a value in -100..100

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "filter_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYes

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?

With no annotations supplied, the description carries the full behavioral burden and discloses little: it does not say whether the change persists across sessions, whether playback must be active, or what happens on out-of-range/invalid input beyond the schema's rejection. The -100..100 range is already encoded in the schema, so it adds no new behavioral context.

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?

A single tight sentence with zero filler and the operative verb and filter list front-loaded. The pipe-separated enumeration is slightly syntax-heavy but still efficient.

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 two-parameter setter with no output schema and no annotations, the description conveys what the tool does and the accepted filter names. It falls short on side effects, persistence, and state requirements, which matter for a mutation-style tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only restates the enum values and the min/max already present in the schema. It adds no semantic meaning such as what 0 represents (neutral?), how negative vs positive values behave, or how gamma differs from brightness.

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?

States a specific verb ('Set') plus the resource ('a video filter') and enumerates the five adjustable filters, so an agent can distinguish it from filter_list and filter_reset at a glance. It stops short of explicitly contrasting itself with those siblings, which keeps it from a 5.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as a loaded video, and no named alternatives (e.g., filter_reset to return to defaults). Usage is only implied by the verb 'Set'.

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