Skip to main content
Glama

Show assets to the user

view
Read-onlyIdempotent

Show the user assets inline — pass artifact_ids (one or many): emero ids ("job:#" / "upload:") or external https image URLs. This NEVER sends them to you: to look at an asset yourself, or read its exact prompt + settings, use inspect. NEVER stores — to KEEP an external image for reuse, use ingest_url after you've chosen it. Do NOT call view on a generation you just made: check_generation already showed it to the user.

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": {
      "artifact_ids": "<artifact_ids>",
      "project_id": "<project_id>"
    },
    "name": "view"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
show_userNo
project_idYesOpaque per-chat project id: "p-" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list.
artifact_idsYes
return_imageNo
include_detailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Opaque per-chat project id. Mint one on your first emero action, pass that SAME id every call. One project per chat: NEVER mint a second for a new topic/campaign/subject/vibe — all stay in the one project; a new id is only for a new chat (server folds a stray id back in). A new chat the user says continues an earlier project reuses that project's id (from get_emero_brain's project list)."New value: +"Opaque per-chat project id: \"p-\" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the safety hints, it adds critical behavioral guarantees about data handling, specifically stating it 'NEVER sends them to you' and 'NEVER stores' images, which are vital constraints for an agent.

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?

The description is dense, which is necessary given the low schema coverage and high complexity. It uses formatting and front-loading effectively to deliver critical, high-value information immediately.

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?

Due to the inadequacy of the input schema, the description is maximally complete. It addresses purpose, data sensitivity, input structure, and appropriate tool routing to handle all agent intent related to asset viewing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given the extremely low schema coverage (17%), the description is essential. It specifies the required format for `artifact_ids`, defining both internal formats (`job:<uuid>#<index>`, `upload:<id>`) and external URLs.

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 clearly states the purpose as showing assets inline. Crucially, it provides immediate differentiation from the `inspect` sibling by specifying that while `view` shows the asset, `inspect` is used to read details like prompt and settings.

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 provides multiple explicit usage constraints and negative constraints: one must not call it on a fresh generation (direct agent to `check_generation`), one must not store external images (direct agent to `ingest_url`), and one must use `inspect` for detailed metadata.

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.