Skip to main content
Glama

view_inspo

Display archive images from given paths so you can inspect composition, color, typography, and layout. Use paths from search or recent results; up to 12 images per call.

Instructions

Look at specific items from the archive. Takes paths from search_inspo or recent_inspo.

Returns the images themselves so they can actually be examined — composition, color, type, layout. This is the tool that makes the archive useful rather than merely listed.

Images come back downscaled to roughly 640px on the long edge, which is enough to read a layout and a palette. Ask for full resolution only when fine detail genuinely matters. Videos return their poster frame, since a still is all that can be shown.

Costly: each image is roughly 1-2k tokens, and at most 12 are returned per call. Search first and choose deliberately.

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": {
      "paths": "<paths>"
    },
    "name": "view_inspo"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesArchive-relative paths, e.g. "riso/Riso (1).jpg". At most 12.
fullSizeNoReturn the original instead of the downscaled version. Much more expensive; only for fine detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses output resolution (~640px long edge), the video fallback (poster frame only), per-image token cost (1-2k), and the 12-item ceiling per call. These are exactly the operational facts an agent needs before spending context.

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?

Resolution and return format are front-loaded, followed by cost guidance, which is the right order. Slightly padded by editorial asides ("makes the archive useful rather than merely listed"), but no sentence creates ambiguity.

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?

There is no output schema and no annotations, so the description must cover return behavior itself, and it does: image format, downscaling, video handling, per-call cap, and cost. Nothing an agent needs to call this 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 genuine meaning: it explains where `paths` values originate and frames `fullSize` as a cost tradeoff rather than just a boolean, reinforcing the schema's "only for fine detail" note.

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 ("Look at specific items from the archive") and immediately clarifies what it returns: the images themselves rather than metadata. It also names the sibling tools that produce its inputs (search_inspo, recent_inspo), so an agent can distinguish viewing from searching without opening a schema.

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?

Explicitly gives the prerequisite (paths must come from search_inspo or recent_inspo), an explicit cost-based exclusion ("Ask for full resolution only when fine detail genuinely matters"), and procedural guidance ("Search first and choose deliberately"). The when-not-to-use-fullSize rule is stated outright.

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