Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Attachment keep

attachment_keep

Makes a picture the owner sent one of the business's own pictures (Create's library, which later pictures and films pick from; read for the brand's look on the owner's tokens, as every picture they add is) and gives its file id for what you make. Use it only when the owner says the picture is theirs to keep, or asks for it in something you make; never for a picture of someone else's they sent to talk about. It needs an act key.

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": {
      "id": "<id>"
    },
    "name": "attachment_keep"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe picture's id, from input.attached or attachment_read
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses that the picture is durably copied into the brand's library that later pictures and films draw from, that a file id is returned, and that an act key is required. It does not discuss reversibility, limits, or what happens on repeat calls.

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

Conciseness2/5

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

All the content is relevant, but it is delivered as one long run-on sentence with nested parentheticals ('Create's library, which later pictures and films pick from; read for the brand's look on the owner's tokens, as every picture they add is') that forces re-parsing. The core action and the usage rule should be front-loaded in separate sentences.

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 two-parameter, non-destructive mutation with no output schema, the description covers what it does, when to use it, when not to, the auth prerequisite, and the returned file id. Only side-effect details (duplicate handling, whether the source attachment remains) are missing.

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% and the schema already explains both id (source: input.attached or attachment_read) and project. The description adds no parameter-level meaning and never mentions the optional project parameter, so the 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?

The description does state the transformation (an owner-sent picture becomes one of the business's own pictures in Create's library) and the result (a file id for use in what the agent makes). The verb phrasing is tangled and no sibling is named explicitly, but the action and outcome are recoverable.

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?

It gives an explicit positive condition (owner says the picture is theirs to keep, or asks for it in something you make) and an explicit exclusion (never for someone else's picture sent just to talk about), which implicitly routes conversational images to attachment_read instead. This is exactly the when/when-not guidance an agent needs.

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

All Marsell 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