Skip to main content
Glama

Request photo upload link

klynx_request_photo_upload

Use this when the user has a photo on their phone or computer, or attached to the chat, and there is no public https link to it. Creates a private one-time upload link that accepts one photo within 15 minutes. Free, takes no inputs. Returns upload_id, upload_url (a page where the owner chooses the photo), upload_api_url (an endpoint that accepts the photo bytes) and expires_at. Once the photo is uploaded, the upload_id is the photo input for klynx_check_photo and klynx_create_post_pack. It does not enhance, caption or publish anything.

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_request_photo_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
next_stepYes
upload_idYes
expires_atYes
upload_urlYesA page where the owner chooses the photo.
upload_api_urlYesAn endpoint that accepts the photo bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly given. The description adds genuinely useful behavior beyond the annotations: one-time use, a 15-minute expiry, no cost, and the four returned fields. It stops short of stating failure modes (expired link, second upload attempt, wrong file type), which an agent would want for a time-boxed resource.

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?

Front-loaded with the trigger condition, then the mechanism, then the return fields and chaining, then a negative scope statement. Every sentence carries selection-relevant information and nothing is padded.

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

Completeness5/5

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

An output schema exists, yet the description still names the return fields because upload_id is the hand-off key to klynx_check_photo and klynx_create_post_pack — that chaining context is the missing piece an agent would otherwise lack. For a no-input, non-idempotent link-minting tool, nothing essential is absent.

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?

There are zero parameters and schema coverage is 100%, so the baseline is 4. "Free, takes no inputs" restates what the empty schema already shows but correctly reassures the agent nothing must be supplied.

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 — "Creates a private one-time upload link that accepts one photo within 15 minutes" — plus the trigger condition (no public https link). It also names the downstream tools that consume the resulting upload_id, so an agent can distinguish this from klynx_create_post_pack or klynx_get_connect_link without opening another schema.

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

Usage Guidelines5/5

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

Gives an explicit activation condition (user has a photo on phone/computer or in chat, and no public https URL) and an explicit exclusion of adjacent behavior ("does not enhance, caption or publish anything"), routing those jobs elsewhere. It also says what to do after upload, which is the guidance an agent needs to chain tools.

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