Skip to main content
Glama

set_output_blanking

Sets timeline output blanking in pixels to add letterbox or pillarbox borders on the top, bottom, left, and right.

Instructions

Timeline output blanking in pixels (letterbox / pillarbox).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_output_blanking"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
leftNo
rightNo
bottomNo
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, so the agent knows this mutates state non-destructively, but the description adds nothing beyond that. It does not say whether omitted edges keep their current values or reset to the schema default of 0, nor whether the change is applied immediately or is undoable – significant for a mutation tool with four defaulted parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is extremely short and free of padding, but it is a sentence fragment rather than a front-loaded statement of action and scope. Terseness here reflects under-specification rather than disciplined editing.

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?

A five-parameter mutation tool with no schema descriptions, no output schema, and no annotation detail beyond safety hints needs far more: what each edge does, what 'timeline' selects, and what happens when an argument is omitted. The definition leaves an agent unable to call this confidently beyond guessing.

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 carries the full burden for five parameters and largely fails: it implies the four edge margins correspond to top/left/right/bottom in pixels but gives no meaning for the 'timeline' parameter or for how the defaults behave. Only the unit convention is clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names the resource (timeline output blanking) and clarifies the unit and effect with 'pixels (letterbox / pillarbox)', which helps an agent understand intent. However, it never states a verb and never distinguishes itself from timeline-level siblings such as set_timeline_settings, so the purpose is only implied from the tool name.

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 guidance, no mention of when not to call it, and no named alternative. The agent must infer entirely from the tool name that this sets blanking margins rather than reading or clearing them.

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