Skip to main content
Glama

Image crop and contain fit

bpj_image_frame_fit
Read-onlyIdempotent

Estimate cover cropping, contain letterboxing and a CSS aspect ratio from supplied dimensions.

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>",
      "targetWidth": "<targetWidth>",
      "targetHeight": "<targetHeight>"
    },
    "name": "bpj_image_frame_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes
targetWidthYes
targetHeightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare the generic safe-read profile (readOnly, idempotent, non-destructive, closed-world). The description adds no behavioral detail beyond that: it does not say whether this is pure local math or a network/asset fetch, what units or rounding are applied, or what the computed result contains — a real gap given there is no output schema.

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?

One front-loaded sentence with no filler; every clause names a distinct output (crop, letterbox, aspect ratio). It is short to the point of under-specification rather than bloated.

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-required-parameter, zero-coverage, no-output-schema tool, the description leaves too much unsaid: no explanation of what values come back (crop rectangles, offsets, an aspect-ratio string such as '16/9'), no rounding/format rules, and no note on how the three outputs relate to the inputs.

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 0% and only property titles ('Source width', 'Frame width', etc.) carry meaning. The description partially compensates by separating the source image ('cover/contain') from the target frame implied by the alternative fits, giving the reader a hint that width/height are source dims and targetWidth/targetHeight are the frame.

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 computation: cover cropping, contain letterboxing, and a CSS aspect ratio derived from supplied dimensions. A reader knows it is a geometry/measurement tool, though the verb 'estimate' softens precision and no sibling (e.g. bpj_responsive_image_check) is referenced for contrast.

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 mention of cover/contain plus a CSS aspect ratio implies the use case (figuring out how an image fits a frame), but there is no explicit when-to-use, when-not-to-use, or pointer to any alternative tool for related image checks.

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.