Skip to main content
Glama

Leave a product out of peer studies

research_skip

Remove a product the founder says is not like them (sells to other buyers, is far bigger, is not a product at all) from this study's patterns and from every study after it, by its domain or a URL on it. With undo, it can be studied again. Free.

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": {
      "domain": "<domain>"
    },
    "name": "research_skip"
  }
}

Input Schema

NameRequiredDescriptionDefault
undoNotrue to bring a product back that was removed before
domainYesThe product's domain as research gives it (peers[].domain, an app's key for an app), or any URL on it (an app's App Store link)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"The product's domain as research gives it (peers[].domain), or any URL on it"New value: +"The product's domain as research gives it (peers[].domain, an app's key for an app), or any URL on it (an app's App Store link)"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare only non-read-only, non-destructive, non-open-world; the description adds the key behavioral fact that the exclusion persists into every future study, plus that it is reversible via undo and free. Return format is not described, but the tool has no output schema and the observable effect is stated.

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 and its persistence scope are front-loaded, and the trailing clauses (undo, free) are brief and useful. The parenthetical reason list is a little dense but earns its place by enabling the decision.

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 two-parameter mutation with no output schema, the description covers scope, permanence, reversibility, and cost, which is nearly everything needed. Only the state of sibling tools (ideas_skip/listing_skip) is left unaddressed.

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 100%, so both parameters are already documented, including the peers[].domain / App Store link nuance. The description restates the domain-or-URL choice and nothing about the undo parameter, so it adds little beyond the schema.

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 ("Remove a product ... from this study's patterns and from every study after it") plus the identification key (domain or URL). It also separates itself from the similarly named siblings (ideas_skip, listing_skip) by anchoring the action to peer studies.

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 when-to-use criteria in the founder's own terms (sells to other buyers, far bigger, not a product at all), so an agent can decide without guessing. It does not name alternative siblings for the near-miss cases, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources