Skip to main content
Glama

Title safe frame

bpj_design_frame_safe_area
Read-onlyIdempotent

Build a whole-pixel safe rectangle for titles or on-screen graphics with a specified inset on every edge.

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>",
      "inset": "<inset>"
    },
    "name": "bpj_design_frame_safe_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
insetYes
pixelsHighYes
pixelsWideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral detail with 'whole-pixel' rounding and a uniform inset on every edge, but it does not explain the returned rectangle structure or edge-case behavior.

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?

The definition is a single front-loaded sentence with no wasted wording. It communicates the core action, output concept, and inset behavior efficiently.

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

Completeness3/5

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

For a simple calculation tool the description covers the main purpose, and annotations cover safety traits. However, with no output schema and no schema descriptions, it leaves the return shape and exact parameter semantics insufficiently explained.

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 must carry parameter meaning. It implies pixel dimensions and a uniform edge inset, but it does not explicitly clarify that inset is a percentage, does not explain the 0-49 range, and adds little beyond the parameter titles and bounds.

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 a specific verb and resource: build a whole-pixel safe rectangle for titles or on-screen graphics. It is clear what the tool produces, though it does not explicitly differentiate itself from sibling design-calculation tools.

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

Usage Guidelines4/5

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

It gives a clear use context: titles or on-screen graphics with a specified inset on every edge. It does not name exclusions or alternative tools, so it stops short of full when-to-use versus alternative guidance.

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.