Skip to main content
Glama

Remove items from the board

inspo_remove

Remove off-brief, broken, or misplaced references and components, then block them so future harvests don’t re-add them; rerun harvest to refill the section.

Instructions

Remove references/styles/components that are off-brief, broken, or in the wrong section (e.g. a landing page filed under footer). Removed references are blocked so a later harvest never re-adds them; run inspo_harvest again to refill the section.

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": {
      "ids": "<ids>"
    },
    "name": "inspo_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
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

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does add real value by revealing a non-obvious side effect: removed references are blocked so a later harvest never re-adds them. It does not say whether removal is reversible, whether the block can be lifted, what happens to already-placed items, or what the response returns — all material for a mutation tool.

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?

Two sentences with zero filler: the first defines what qualifies for removal, the second front-loads the durable blocking consequence and the recovery step. Every clause carries information an agent needs.

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 destructive mutation with no annotations and no output schema, the description covers the motivation and one important side effect but leaves key gaps: irreversibility of the block, permission requirements, and the identity of the 'ids' argument. Adequate but not complete for a write tool.

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

Parameters2/5

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

Schema coverage is only 50%, and the description adds no meaning to 'ids' at all — the agent still cannot tell whether these are harvest ids, reference ids, section ids, or mixed. The 'session' default is documented in the schema, not the description, so no compensation for the coverage gap occurs.

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?

Uses a concrete verb (remove) applied to a named set of resources (references/styles/components) and illustrates the failure modes it targets, e.g. 'a landing page filed under footer'. It also names the sibling it interacts with (inspo_harvest), so an agent can place it in the workflow 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 clear triggering conditions — off-brief, broken, or wrong-section items — and states the follow-up action, re-running inspo_harvest to refill the section. It stops short of explicit when-not guidance (e.g. when to prefer re-adding or re-filing over removing) and names no true alternative tool.

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