Skip to main content
Glama

Caelara Labs Dynamic Media

aspect_ratio_calc

Reduce dimensions to an aspect ratio, name the closest standard ratio, scale to a target and map to social-media presets

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": "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 observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it never says whether scaling preserves the computed ratio, how rounding is handled, what happens when both target_width and target_height are supplied, or what the returned payload looks like. It also promises 'map to social-media presets' while the schema has no preset parameter, leaving the agent unable to actually request that behavior. Only the enumeration of outputs (ratio, standard name, scaled dims, presets) counts as disclosure.

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 front-loaded sentence with no filler, listing capabilities in a logical order from reduce to name to scale to map. It is dense rather than verbose, though the four-part list reads as a capability dump rather than an ordered workflow.

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?

For a four-parameter calculator with no output schema and no annotations, the description should specify the result shape and the interaction between optional targets; it does neither. The advertised preset mapping has no corresponding input, so an agent cannot tell whether that output is automatic or unreachable. Only the high-coverage schema prevents this from being a 1.

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 100%, so the two integer pairs are already documented at the field level, and the baseline for high coverage is 3. The description adds no per-parameter meaning such as units, constraints, or precedence between target_width and target_height. Its mention of presets does not map to any parameter, so it adds no usable semantic layer.

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 names four concrete capabilities with specific verbs and resources: reducing dimensions to a ratio, naming the closest standard ratio, scaling to a target size, and mapping to social-media presets. That distinguishes it clearly from siblings such as image_meta_inspector or favicon_hd_resolver, which inspect or generate rather than compute ratios. It is not a 5 because it never clarifies that these are four modes of one calculator or how they relate.

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 statement of when to use this tool versus the many sibling generators, nor any exclusion or prerequisite. The agent is left to infer that supplying target_width/target_height triggers scaling and that omitting them yields only ratio reduction, and nothing warns about whether both targets can be combined. Usage is at best implied by the parameter names, not by the description.

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.

Resources