Skip to main content
Glama

Add a listing photo

attach_deal_photo
Idempotent

Used by the SlabLineage photo panel: saves a photo the user took as the listing photo of a Deal Desk purchase. side front replaces the front photo (a back photo already saved is kept); side back adds a back photo after the current front photo.

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": {
      "dealId": "<dealId>",
      "side": "<side>",
      "imageBase64": "<imageBase64>",
      "mimeType": "<mimeType>"
    },
    "name": "attach_deal_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesfront or back of the card.
dealIdYesThe dealId from record_purchase or prepare_listing.
mimeTypeYesThe photo's type.
imageBase64YesThe photo as base64 data (7 MB at most).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the key mutation semantics that annotations do not capture: 'front' overwrites the existing front photo while preserving the stored back photo, and 'back' inserts after the current front. That is precisely the overwrite scope an agent needs, since destructiveHint=false alone would not reveal that a prior front image is replaced.

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 sentences, no filler, with the source panel stated first and the side semantics second. Dense but readable; nothing is redundant with the schema text.

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 4-required-param mutation with no output schema, the description covers who calls it, what it stores, and how each side value behaves. Remaining gaps (error behavior when no front photo exists for a 'back' add, and what is returned) are minor and largely covered by the fully-described input schema.

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?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by giving 'side' behavior that the schema lacks ('front or back of the card' only), namely the replace-vs-append distinction. dealId, mimeType, and imageBase64 are left to the schema, which documents them fully.

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: 'saves a photo the user took as the listing photo of a Deal Desk purchase', and names the UI surface ('SlabLineage photo panel') that drives it. It does not distinguish itself from listing siblings such as prepare_listing or publish_listing, so it stops short of a 5.

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?

Implied usage is clear (adding a photo to a deal while in the photo panel), and the front/back sentence tells the agent which call fits which situation. There is no explicit when-not guidance or routing to alternatives like prepare_listing, so the guidance is adequate but incomplete.

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