Skip to main content
Glama

Add screens

add_screens

In Claude, shows a box in the chat where the person picks, drops or pastes app screenshots; each goes straight into the brand kit. For screenshots already attached to the chat, send them from your code sandbox first (get_promo's next says how) rather than asking for them again. Pass promo_id (or brand_id). Free. When they say they're done, call make_promo with promo_id (or brand_id).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_screens"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_idNoOr a brand kit, by id or name, when there is no promo yet
promo_idNoThe promo to add screens to, from make_promo; its brand kit takes them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds real behavior: this is an interactive chat box that waits on the human, its output lands directly in the brand kit, and the call is free. It does not say what happens if the person cancels or submits nothing, which keeps it short of 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 behavior and then sequenced as guidance, prerequisites, cost, and next step. Dense but mostly earning its words, with the parenthetical "(get_promo's next says how)" being slightly oblique pointer text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter interactive tool with no output schema, the description covers what it does, how to invoke it, the alternate ingestion path, cost, and the required follow-up call. Nothing an agent needs to call it correctly is missing.

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 adds meaning the schema does not encode as a constraint: "Pass promo_id (or brand_id)" communicates the one-of requirement that the schema leaves implicit with zero required fields. That resolves a genuine ambiguity about what must be supplied.

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?

"Shows a box in the chat where the person picks, drops or pastes app screenshots; each goes straight into the brand kit" states a concrete verb, resource, and destination for the collected images. An agent can tell this is an interactive collection widget rather than an ingestion API, though it never explicitly contrasts itself with alternatives such as screens_from_recording.

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 the condition to use it (the person needs to supply screenshots), an explicit prohibition with an alternative path (for already-attached screenshots, send from the code sandbox per get_promo rather than asking again), and a clear follow-up (call make_promo when the user says they're done). Both the when and the when-not are stated.

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