Skip to main content
Glama
Sign In

lobstermatch

by com.lobstermatch
OverviewDiscussionsAdmin

Upload a project image

upload_project_image
Idempotent

Upload or remove a project image. At most 5 images, 500 KB each, png, jpeg, or webp. Bytes are stored by LobsterMatch and served from this origin. Metadata is stripped. Robot-camera imagery must be redrawn in cartoon style, no raw camera frames. A published page does not show a new image until the page is approved again. One project write when the set changes, plus one object write for a new image.

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": {
      "slug": "<slug>"
    },
    "name": "upload_project_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
altNoWhat the image shows. Required when uploading.
dataNoBase64 image bytes. Required when uploading. At most 500 KB after decoding.
slugYesProject slug.
actionNoupload or remove. upload is the default.
imageIdNoImage id to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare destructiveHint=false, but the description says the tool can remove a project image. Removal is a destructive update, so the description contradicts the annotation. The description otherwise adds useful behavioral detail about storage, metadata stripping, approval state, and write counts.

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?

The description is front-loaded with the core action, then adds constraints and behavioral rules in dense but substantive sentences. Each sentence contributes operational context without obvious filler.

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 mutation tool, the description covers important constraints, storage behavior, approval semantics, and write counts. It is nearly complete, though without an output schema it could say more about what an upload or removal returns.

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 the schema already documents all five parameters. The description adds set-level constraints such as max 5 images and allowed formats, but it does not clarify per-parameter meaning beyond what the schema provides.

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?

The description states specific verbs and resource: upload or remove a project image. This clearly distinguishes the tool from siblings like update_project, create_project, and review_project.

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?

It gives clear usage context and constraints, including the 5-image limit, supported formats, and that raw robot-camera frames are not allowed. However, it does not explicitly name alternative tools or state when not to use this one beyond the camera-style rule.

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

All lobstermatch toolsInspect
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