MyImage2Life

Make a plan

create_plan

Saves the agreed gift idea as a plan: the product, what goes on it, the style and any text, and whether the user's own photo is used. Returns a link to the MyImage2Life website, where the user makes the design, sees the proof and price, and orders. Nothing is created or charged by this tool.

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": {
      "product": "<product>",
      "idea": "<idea>"
    },
    "name": "create_plan"
  }
}

Input Schema

Name	Required	Description	Default
`idea`	Yes	What goes on the product: subject, composition, colours and mood, in a few rich sentences. For the user's own photo: what to do with it
`kind`	No	new_design = a design is made from the idea on the website; own_photo = the user uploads their own photo on the website	new_design
`text`	No	Optional exact text on the product, e.g. 'Happy birthday Sanne'
`style`	No	Optional illustration style
`product`	Yes	Product reference from search_products
`language`	No	Language of the user: nl or en	en
`recipient`	No	Optional: who it is for and the occasion, e.g. 'grandma, 80th birthday'

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description usefully adds that nothing is created or charged and that a website link is returned — valuable context for a write-flagged tool. It does not address idempotency (idempotentHint=false) or what happens on repeated calls, which is a real gap for a save operation.

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

Conciseness4/5

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

Three sentences, front-loaded with what is saved, followed by the return value and the safety clarification. Every sentence carries information, though the field enumeration in sentence one slightly overlaps the schema.

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 7-parameter tool with full schema coverage and no output schema, the description covers purpose, the returned link, and the no-charge guarantee, which is what an agent most needs. Minor gaps around idempotency and the optional language/recipient fields keep it from a 5.

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 100%, so the baseline is 3. The description echoes the main fields (product, what goes on it, style, text, own photo) but adds no format or constraint detail, and leaves 'language' and 'recipient' entirely to the schema.

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 specific verb and resource ('Saves the agreed gift idea as a plan') and enumerates what the plan captures: product, idea, style, text, and own-photo usage. It does not name a sibling explicitly, but the closing line ('Nothing is created or charged') implicitly separates it from create_design and place_order.

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 phrase 'agreed gift idea' implies the tool is used after the user has settled on a concept, and the mention of the website hand-off implies it is not for design generation or ordering. However, no alternative tool is named and there is no explicit when-not-to-use guidance, so usage must be inferred.

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

All MyImage2Life 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?