Skip to main content
Glama

Open the voting board

inspo_open

Open the local design review board in your browser to vote on references, styles, lab components, or page sections. Collect feedback, notes, and tags that autosave, then submit the round.

Instructions

Start (if needed) and open the local board in the user's browser. Tabs: References (by section), Styles, Lab (live 3D/motion components), Page (the built page, with per-section feedback), Brief. The user likes/dislikes, stars, tags reasons and writes notes; everything autosaves, and "Send" marks the round as submitted.

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": "inspo_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNo
openNoOpen the browser (default true).
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses idempotent start-up, browser opening, the autosave behavior, and that "Send" submits a round, but says nothing about authentication (inspo_login exists as a sibling), whether the call blocks, or what happens if a session is already open.

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 core action is front-loaded in the first sentence, and the tab list is a compact enumeration. The final clause about user likes/stars/notes and "Send" describes human UI behavior more than tool invocation, but it does explain a consequential side effect.

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

Completeness3/5

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

For a zero-required-parameter tool with no output schema and no annotations, the description covers the observable effects well. Gaps remain: no mention of what the tool returns, whether a local server/port must already exist, or the unexplained "plan" tab value.

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 description coverage is 67% and the description adds real meaning to the tab enum by explaining what References, Styles, Lab, Page, and Brief each contain. However, the enum also includes "plan", which the description never mentions, and it does not map its prose labels back to the enum values explicitly.

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?

States a specific compound action ("Start (if needed) and open the local board in the user's browser"), which also pre-empts confusion with the sibling inspo_start by noting the start is conditional. The resource and effect are unambiguous, though no sibling is named outright.

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

Usage Guidelines3/5

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

Usage is implied: you call this to bring up the voting/board UI. There is no explicit when-not guidance (e.g. when to call inspo_status, inspo_start, or inspo_feedback directly instead), so the agent must infer its place in the workflow.

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