Skip to main content
Glama

Anamorphic desqueeze dimensions

bpj_design_anamor_desqueeze
Read-onlyIdempotent

Calculate display width and aspect ratio after horizontal desqueeze of anamorphic footage.

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": {
      "pixelsWide": "<pixelsWide>",
      "pixelsHigh": "<pixelsHigh>",
      "squeeze": "<squeeze>"
    },
    "name": "bpj_design_anamor_desqueeze"
  }
}

Input Schema

NameRequiredDescriptionDefault
squeezeYes
pixelsHighYes
pixelsWideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds that the result is a display width plus an aspect ratio, which is useful since no output schema exists, but it omits the actual relationship (whether height stays fixed, rounding behavior, units of the squeeze factor beyond the schema title).

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?

A single front-loaded sentence with the operation and both outputs stated up front. No filler, no repetition of the title.

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

Completeness4/5

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

For a three-parameter pure calculation with full annotation coverage and no output schema, the description names both return values and the operation, which is close to sufficient. It could be tightened by stating that height is unchanged and that width is scaled by the squeeze factor.

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?

Schema description coverage is 0%, so the description must carry the burden; it partially does by specifying that the squeeze is horizontal and is applied to footage, which disambiguates the direction of the factor. It adds nothing about how pixelsWide/pixelsHigh are consumed or what the default display height assumption is.

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?

Specific verb 'Calculate' plus concrete outputs ('display width and aspect ratio') and a named domain operation ('horizontal desqueeze of anamorphic footage'). An agent can tell exactly what computation happens, though the description doesn't contrast against any sibling calculator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'after horizontal desqueeze of anamorphic footage' implies the usage context, but there is no explicit when-to-use rule, no exclusions, and no pointer to an alternative (e.g. a squeeze-factor or lens calculator sibling). Usage must be inferred from the purpose statement.

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.