Skip to main content
Glama

Cross Stitch Pattern Maker

Get photo upload link

get_photo_upload_link
Read-only

Get a link where the person can upload a photo from their phone or computer. Use this when the person has a photo on their device but you have no public URL for it. After the upload, the page shows a photo code (ph_...). Pass that code as photo_id to create_cross_stitch_pattern.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the crucial non-obvious trait that a human completes the upload out-of-band and the agent must read the resulting code off the page. It stops short of stating link expiry, whether the code is returned by the tool or only displayed to the user, or any waiting/polling expectation.

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?

Three short sentences: purpose first, then the use condition, then the handoff to the sibling tool. No filler, and the most decision-relevant clause is front-loaded.

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?

With no parameters and no output schema, the description carries the return-value burden and does explain what comes back (a link) and what follows (a ph_... photo code). The remaining gap is operational: it doesn't say how the agent obtains the code or how long the link stays valid.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly spends no words on parameter semantics.

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 ("Get a link where the person can upload a photo") and immediately contrasts it with the case where a public URL already exists. An agent can distinguish this from create_cross_stitch_pattern or get_kit_prices without opening any 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 trigger ("the person has a photo on their device but you have no public URL for it") plus the downstream action (pass the resulting ph_... code as photo_id to create_cross_stitch_pattern). Both when-to-use and what-to-do-next are spelled out rather than implied.

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.