Skip to main content
Glama
BlueVetaUpright MCP server

BlueVetaUpright MCP server

by Tomerbarm

Detect and fix a product photo's rotation

detect_rotation

Checks whether a product photo is upright or sideways and returns the exact clockwise degrees needed to correct it, plus a confidence score and an uncertainty flag.

Instructions

Checks whether a product photo is upright and, if not, exactly how many degrees to rotate it (clockwise). Returns a confidence score and an honest flag when the answer is uncertain. Bills the caller's own BlueVetaUpright account per call, same as the REST API -- requires an API key from https://blueveta.com/upright, set as BLUEVETA_UPRIGHT_API_KEY or passed as apiKey.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "detect_rotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoOverrides the BLUEVETA_UPRIGHT_API_KEY environment variable for this call
imageUrlNoA hosted image URL for BlueVetaUpright to fetch
imageBase64NoRaw image bytes, base64-encoded (use this OR imageUrl, not both)
returnImageNoAlso return the corrected image (priced 1.5x, same as the REST API)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden, and it does add real value: per-call billing against the caller's own BlueVetaUpright account, an API key requirement with its env var name, and an 'honest flag' for uncertain answers. However, it never says whether the tool itself rotates the image or only reports degrees -- the title claims 'detect and fix' while the body describes detection only, leaving a genuine ambiguity about the mutation behavior.

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?

Three tight sentences, front-loaded with what the tool does, then returns, then commercial/credential terms. Every clause carries information; no filler or marketing padding.

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?

Return values are described well enough to compensate for the missing output schema, and billing/auth are covered. What is left open is operationally important: with zero required parameters, the description never states what happens if neither imageUrl nor imageBase64 is supplied, nor which image formats are accepted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description adds context by tying apiKey to the account billed and by naming the environment variable and signup URL, which the schema only references briefly. It does not clarify the zero-required-parameter situation (neither imageUrl nor imageBase64 is mandatory).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource -- checks whether a product photo is upright and returns the exact clockwise rotation in degrees -- and names the concrete return values (degrees, confidence, uncertainty flag). An agent knows precisely what it gets back without opening a schema.

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 context of use (product photos that may be mis-rotated) is implied by the wording, but there is no explicit when-to-use versus when-not guidance, no statement about supported image types, and no alternatives to compare against. Since no siblings exist, the absence of routing guidance is less damaging, but the description still leaves usage conditions implicit.

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