Skip to main content
Glama

Paint by Numbers Generator

Get a photo upload link

get_photo_upload_link
Read-only

Get a web page link where the person can upload a photo from their phone or computer. The page then shows an image URL to paste back into the chat, for use with create_paint_by_numbers. Use this when the photo is only on the person's device.

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.5/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, and the description does not contradict them — retrieving a link is a non-destructive read. Beyond the annotations it adds genuinely useful behavior: the flow depends on the human completing an external step and copying a URL back, and the tool produces no useful value until they do. It omits whether the link expires or requires auth, which would have earned a 5.

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?

Two sentences, front-loaded with the mechanism and then the usage condition. Nothing is redundant and no sentence could be cut without losing a distinct piece of information (link purpose, return value, precondition).

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?

For a zero-parameter tool with no output schema, the description covers everything an agent needs: what it returns, how the result comes back into the conversation, and the precondition for using it. The hand-off to create_paint_by_numbers closes the loop.

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 per the baseline this scores 4. The description correctly implies that no inputs are needed — the only variable is who will open the link, which is handled out-of-band.

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 web page link where the person can upload a photo') and immediately frames the outcome: the page hands back an image URL. It also names the downstream consumer, create_paint_by_numbers, so an agent knows exactly where this fits in the workflow.

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?

Gives an explicit selection condition: 'Use this when the photo is only on the person's device.' That implicitly excludes the case where a usable image URL already exists, though it never states the alternative path outright or what to do if the upload page is abandoned.

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