Skip to main content
Glama

Check photo suitability

klynx_check_photo
Read-onlyIdempotent

Use this when the user wants to know whether a photo is good enough for a social media post, or before klynx_create_post_pack on a photo not used before. Needs image_url (https) or upload_id (from klynx_request_photo_upload). Free and changes nothing. Returns a 0 to 100 suitability score, suitable (true or false), brightness, clipped shadows and highlights, sharpness and blur, whether people or hands are in frame, whether it is a photograph (reported for information only), a short description of the subject, up to three issues and the longest edge in pixels. A photo under 800px on its longest edge is reported as not suitable with reason photo_too_small. It does not enhance or caption the photo.

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": "klynx_check_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlNohttps URL of a JPEG, PNG or WebP photo, up to 20MB. Send this or upload_id, not both.
upload_idNoupload_id from klynx_request_photo_upload, once the photo has been uploaded. Send this or image_url, not both.

Output Schema

NameRequiredDescriptionDefault
blurYes
scoreYes0 to 100.
issuesYes
reasonYesphoto_too_small when the longest edge is under 800px, otherwise null.
subjectYes
suitableYes
reel_noteNoHow the photo is framed on a Reel.
sharpnessYes
brightnessYes
orientationNoportrait when taller than wide, otherwise landscape.
operation_idYes
people_countYes
hands_visibleYes
is_photographYestrue for a photograph, false for an illustration, screenshot or AI-generated image. Reported for information; it does not affect suitable.
clipped_shadowsYes
longest_edge_pxYes
brightness_labelYes
clipped_highlightsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'free and changes nothing' largely restates them. Beyond the structured data it adds two genuine behavioral facts: the hard 800px longest-edge rule that forces photo_too_small, and the fact that it does not enhance or caption. That is useful non-obvious behavior, though it stops short of noting cost limits, rate limits, or how the score is computed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Usage guidance is correctly front-loaded, but the long mid-sentence enumeration of every returned field duplicates the existing output schema and crowds out the genuinely valuable parts. It is not padded with filler, yet roughly a third of the text earns no place given structured output is available.

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

Completeness4/5

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

For a two-parameter, read-only check with an output schema and full annotation coverage, the description covers purpose, timing, inputs and the one threshold that changes the verdict. The only redundancy is restating return fields that the output schema already defines.

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 schema already documents both parameters, their formats and the mutual-exclusivity rule. The description only repeats the https/upload_id sourcing without adding syntax, size, or edge-case detail beyond what the properties state. Baseline 3 is appropriate.

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?

The description states a specific verb and resource ('check' a 'photo' for 'suitability for a social media post') and explicitly distinguishes it from siblings by naming klynx_create_post_pack and klynx_request_photo_upload. An agent can tell what it does and what it does not do ('does not enhance or caption the photo') without touching the schema.

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 trigger ('when the user wants to know whether a photo is good enough for a social media post') and a workflow position ('before klynx_create_post_pack on a photo not used before'), plus points to klynx_request_photo_upload as the source of upload_id. It lacks an explicit when-not/exclusion statement, but the intended timing is unambiguous.

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