Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_aspect_ratio_calc

Reduce dimensions to an aspect ratio, name the closest standard ratio, and scale width or height to targets or social-media presets.

Instructions

[Dynamic Media] Reduce dimensions to an aspect ratio, name the closest standard ratio, scale to a target and map to social-media presets Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "caelara_media_aspect_ratio_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesWidth
heightYesHeight
target_widthNoScale to this width
target_heightNoScale to this height

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully supplies measured latency (p50 12 ms, p95 42 ms with a dated benchmark source) and the backing endpoint, but never states that this is a pure, side-effect-free computation or what happens when target_width and target_height conflict.

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 capability statement is front-loaded in a single dense sentence, followed by a short provenance line; nothing is padding. Minor flaw: the sentence runs from 'presets' straight into 'Measured' with no separator, making the benchmark clause visually merge with the capability list.

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 four-parameter pure calculator with no output schema and no annotations, the description enumerates the four computed results and discloses performance characteristics, which is close to sufficient. The main residual gap is output shape and handling of the optional scaling pair.

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 coverage is 100%, so the baseline is 3. The schema's own descriptions are bare ('Width', 'Height', 'Scale to this width'), and the description adds only that scaling is toward 'a target' without clarifying precedence when both target dimensions are supplied or what units/limits apply.

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?

The description states specific operations on a specific resource: reduce width/height to an aspect ratio, name the closest standard ratio, scale to a target, and map to social-media presets. It is clearly a media-dimension calculator, distinguishable from the geo, ecom, and agent siblings, though it does not explicitly contrast itself with any named alternative.

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?

Usage is only implied by the outputs it produces (aspect ratio, standard-ratio name, scaled dimensions, preset mapping), which suggests when an agent would want it. There is no explicit when-to-use, when-not-to-use, or prerequisite statement.

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