Skip to main content
Glama

Look at a website or running app

inspo_analyze

Analyze any URL to capture a screenshot and extract its fonts, colors, radii, type scale, and tech stack, helping you understand the current app before proposing design directions.

Instructions

Open a URL (including http://localhost for the user's running app), return a screenshot you can see plus its fonts, colors, radii, type scale and tech. Use it to understand the current app before proposing directions. Does not add anything to the board.

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": {
      "url": "<url>"
    },
    "name": "inspo_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key traits: it performs no board mutation, it inspects a localhost-served app, and it returns a viewable screenshot plus design tokens. It leaves out failure behavior for unreachable URLs, latency, and whether authenticated pages need the login sibling — the remaining gaps.

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

Conciseness5/5

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

Three short, front-loaded sentences: action, return payload, usage context, and the non-mutation caveat. No filler, and the most decision-relevant facts come first.

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 one-parameter read tool with no output schema, the description covers purpose, usage context, return contents, and side effects, which is nearly everything an agent needs. Only failure/timeout behavior and the relationship to the login sibling are unaddressed.

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 0% for the single url parameter, so the description must compensate, and it does add real meaning: the URL may be http://localhost for the user's running app, which is non-obvious for a plain uri-formatted string. It adds no further detail on paths, auth-gated pages, or invalid-input behavior.

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 ("Open a URL... return a screenshot plus its fonts, colors, radii, type scale and tech") and enumerates the returned artifacts, so an agent knows exactly what it gets back. It also explicitly carves itself out from the board-mutating siblings with "Does not add anything to the board."

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

Usage Guidelines4/5

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

Gives a clear usage context: "Use it to understand the current app before proposing directions," which tells the agent where this fits in the workflow. It stops short of naming a concrete alternative (e.g. capture vs. analyze) or stating when not to use it, so it is clear but not exhaustive.

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