Skip to main content
Glama

Panorama shot count

bpj_design_panorama_frames
Read-onlyIdempotent

Find the minimum number of frames for an open panorama sweep with a specified angular overlap.

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": {
      "sweep": "<sweep>",
      "field": "<field>",
      "overlap": "<overlap>"
    },
    "name": "bpj_design_panorama_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
sweepYes
overlapYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-open-world, so the safety profile is covered structurally; the description only reinforces that this is a pure calculation. It does not disclose the calculation model (is the frame count rounded up? is overlap treated as a percentage of frame width or of the swept angle?), which is the behavior an agent actually needs.

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 verb and output first, no filler, and no repetition of the title. Nothing here could be cut without losing content.

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 three-numeric-parameter pure-function tool with no output schema, the description should at least pin down rounding and edge cases (sweep smaller than a single frame, overlap near 99%). It defines the problem well but stops short of the details needed to predict the returned integer in boundary cases.

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 the parameter burden and it largely does not. It names 'sweep' and 'overlap' loosely but never explains 'field' (per-frame horizontal field of view) or the relationship between the three values, leaving units (degrees vs percent) to the schema titles alone.

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 (minimum frame count) over a specific domain object (open panorama sweep with a given angular overlap), so an agent can tell what it returns. It does not name or distinguish itself from any sibling calculator, but the resource itself is distinctive enough that confusion is unlikely.

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 'open panorama sweep' implies the usage context (planning a panorama capture) but there is no explicit when-to-use/when-not or reference to an alternative tool. With no near-duplicate siblings in the catalog the practical risk is low, but the description carries no routing 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.