Skip to main content
Glama

Read the user's votes

inspo_feedback

Read board feedback—likes, dislikes, stars, tags, notes, style/component patterns, and built-page votes—and attach favorite thumbnails to guide revisions; optionally wait for Send.

Instructions

Read likes, dislikes, stars, reason tags and notes from the board: per section (bySection), styles, components, patterns (fonts, colors, tech, layouts shared by the likes) and feedback on the built page (build: per-section votes + click-comments). With wait:true, blocks until the user presses "Send" (or timeout). Attaches thumbnails of favorites (spread across sections) so you can see them; pass section to focus on one.

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_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
imagesNoHow many liked thumbnails to attach (default 6).
sectionNoOnly this section's references (and its thumbnails).
sessionNoSession id. Defaults to the most recent session in this project.
timeoutSecNoDefault 240.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole burden and does well: it discloses the blocking/synchronous behavior of wait:true, the existence of a timeout, and that thumbnails are attached to the response (a real context-cost trait an agent needs to know). It does not cover failure modes such as what happens when no session exists or when the timeout fires, leaving some behavioral gaps.

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?

Purpose is front-loaded in the first clause and every sentence carries operational information. The first sentence is heavily parenthesized and run-on, which costs some readability, but no sentence is filler.

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 no-output-schema, multi-section read tool, the description successfully enumerates the returned data groups and the image-attachment behavior. Remaining gaps are minor: timeout outcome, error behavior with no session, and whether the vote payload is included for the `build` bucket alongside click-comments.

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 80% (images, section, session, timeoutSec documented; wait undocumented), and the description compensates by explaining wait:true's blocking semantics, the section-scoping effect on returned references and thumbnails, and that thumbnails spread across sections by default. This adds genuine meaning beyond the schema rather than restating field descriptions.

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?

Opens with a specific verb+resource ('Read likes, dislikes, stars, reason tags and notes from the board') and then enumerates exactly which result groups come back (bySection, styles, components, patterns, build feedback). This is clearly a read/vote-collection tool, distinguishable from the inspo_add_*, inspo_search, and inspo_status siblings without opening the schema.

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 concrete mode-selection guidance: use wait:true to block until the user presses 'Send' (or hit the timeout), and pass `section` to focus on one section. It stops short of stating when NOT to use it or naming an alternative tool for a related need, so it is clear context rather than full when/when-not/alternatives coverage.

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