Garden Design MCP Server

upload_reference_photo

Upload labeled house or garden photos as Base64 data URIs to store them in-session, enabling the AI to analyze existing site conditions for garden design.

Instructions

Upload a reference photo (house exterior, current garden). Stored in-session. The AI agent can analyze photos via its own vision capabilities.

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": {
      "dataUri": "<dataUri>",
      "label": "<label>"
    },
    "name": "upload_reference_photo"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes	Label for the photo, e.g., 'House front', 'Garden view from kitchen'
`dataUri`	Yes	Base64 data URI of the image

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.9.3Nov 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait that photos are stored in-session (ephemeral), but omits size/format limits, whether uploading with an existing label overwrites, and what the call returns (an id or nothing), which matters for a write-style tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the action and scope, with zero filler. The third clause about the agent's own vision capabilities is slightly meta but still useful context rather than padding.

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?

For a simple two-parameter tool with a fully described schema and no output schema, most of what an agent needs is present, including the in-session storage lifetime. Missing are the return value and any constraints on image size or re-upload behavior, which leaves a modest gap for an upload operation.

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 description coverage is 100%, so label and dataUri are already fully documented in the schema. The description adds no format, encoding, or size guidance beyond what the schema states, so baseline 3 applies.

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 ("Upload a reference photo") and scopes the content with examples (house exterior, current garden), so an agent can distinguish it from siblings like get_reference_photos or import_state. It doesn't explicitly name a sibling alternative, but the purpose is unambiguous.

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?

Usage is only implied by the parenthetical examples of what kinds of photos to upload; there is no explicit when-to-use, when-not-to-use, or pointer to get_reference_photos for retrieval. Adequate but leaves the agent to infer the workflow.

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

Deploy Server