Letter IRL

Confirm an uploaded image

confirm_uploaded_image

Idempotent

Internal widget relay that confirms an uploaded image and returns the imageUrl plus next-step guidance. Not intended for direct user requests.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "imageUrl": "<imageUrl>"
    },
    "name": "confirm_uploaded_image"
  }
}

Input Schema

Name	Required	Description	Default
`context`	No	What the photo is for: 'postcard', 'header_image' or 'inline_image'.
`imageUrl`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`imageUrl`	Yes
`suggestedNextStep`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already disclose idempotency, non-destructiveness and a closed-world scope, so the safety profile is covered. The description adds two pieces of context beyond that — that this is an internal widget relay and that the response carries the imageUrl plus next-step guidance — but it never says what 'confirming' actually changes on the server, which matters because readOnlyHint is false.

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 short sentences, no redundancy, and the key framing ('internal widget relay') is front-loaded before the exclusion clause. Every clause carries information an agent needs.

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?

The tool is simple, an output schema exists so return values need no elaboration, and annotations cover safety. The remaining gap is workflow context: the description does not explain its relationship to upload_image or what state transition 'confirm' represents, which an agent needs in order to sequence the two calls correctly.

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 coverage is 50%: the 'context' parameter is well documented in-schema with enumerated values, while 'imageUrl' has no description at all. The description only weakly compensates by implying imageUrl is the URL of an already-uploaded image, and says nothing about accepted formats, origin, or length constraints.

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

Purpose4/5

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

States a concrete verb and resource ('confirms an uploaded image') and mentions what comes back ('returns the imageUrl plus next-step guidance'). It implicitly distinguishes itself from the sibling upload_image by operating on an already-uploaded image, but never names that sibling or the upload-to-confirm sequence directly.

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 exclusion 'Not intended for direct user requests' is a genuinely useful negative guideline, telling the agent not to reach for this on a user's behalf. However, there is no positive trigger, no indication of which tool should be called first (upload_image), and no statement of what condition makes this call appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Letter IRL tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?