Skip to main content
Glama

fill_spot

Insert a picture into an empty sample spot using its key and a local file path or existing Dinoctor image address, with one undo step.

Instructions

Put a picture into an empty picture spot a sample is waiting for (a stand-in person, a photo, a screen or a card's picture). key comes from samples "needs" or "add". Send a picture file from this computer (full path), or the address of a picture Dinoctor already has (starting with /, as generate or upload tools return). One undo step. To put a picture into a shot's cast or background instead, use upload or put_picture.

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": {
      "key": "<key>"
    },
    "name": "fill_spot"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe spot's key from samples "needs" or "add".
urlNoOr: a Dinoctor picture address starting with /.
fileNoFull path of a png, jpg or webp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / key / description
      Added value: +"The spot's key from samples \"needs\" or \"add\"."
    • addedInput schema / properties / url / description
      Added value: +"Or: a Dinoctor picture address starting with /."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds useful behavior beyond them: 'One undo step' tells the agent the write is reversible, and it explains the two input modes (local file path vs an existing Dinoctor address). It does not say what happens if the spot is already filled or what an error looks like, which keeps it from a 5.

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?

Front-loaded with the core action, then the key source, then the input modes, then the undo note, then the alternative routing — a sensible order with no filler. The sentences are long and slightly run-on, but every clause carries information.

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 3-parameter mutation tool with no output schema, the definition covers the action, key provenance, input modes, reversibility, and alternate tools. The remaining gap is edge-case behavior (already-filled spot, handling when both file and url are supplied, failure modes), which is not stated but is not central to selecting the tool.

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 the baseline is 3, but the description goes further: it explains that key originates from samples' "needs" or "add", that url must start with / and comes from generate or upload tools, and that file is a full path on this computer. That origin/format context is genuine meaning beyond the schema's terse field descriptions.

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?

States a specific verb and resource ('Put a picture into an empty picture spot a sample is waiting for') and even elaborates what a spot is (stand-in person, photo, screen, card's picture). It explicitly separates itself from upload and put_picture for cast/background work, so an agent can pick it without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('empty picture spot a sample is waiting for'), names the source of the required key ('from samples "needs" or "add"'), and routes the reader to the alternatives upload or put_picture when targeting a shot's cast or background. Conditions for choosing the sibling are spelled out rather than inferred.

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