Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Set aside

set_aside
Destructive

Not for us: takes communities or rivals that discovery found off the business's lists, as Market's Not for us press does, so no later search lists or studies them again (a subreddit about something else, a rival that is not one). back: true puts ones set aside back. Read discovery_read first and pass each one's name or address as it lists them. Use it when the owner says a community or rival is not theirs or not relevant. Returns the ones set aside or put back, and any name not on file or matching several (pass its address then). It needs an act key.

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": {
      "kind": "<kind>",
      "names": "<names>",
      "back": "<back>"
    },
    "name": "set_aside"
  }
}

Input Schema

NameRequiredDescriptionDefault
backYesfalse: set them aside (Not for us); true: put ones set aside back on the list
kindYescommunity: a place where buyers gather (discovery_read communities); rival: a competitor (discovery_read competitors). One kind per call
namesYeseach one's name or address as discovery_read lists it (a community: r/name or its url; a rival: its name or url)
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key consequence: set-aside items will not appear in later searches or studies, and back=true restores them. It also explains ambiguous-name handling, return behavior, and an act key requirement, all consistent with destructiveHint=true.

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

Conciseness3/5

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

The description is information-dense and front-loads the core purpose, but the prose is awkward, with nested clauses and parentheticals that make it harder to parse than necessary. Some of the set-aside/restore explanation repeats what the schema already says.

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 destructive mutation with no output schema, it covers the main behavioral effects, restoration, prerequisites, return cases, and disambiguation guidance. The unexplained act key and limited project/account context are minor completeness gaps.

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 100%, so the baseline is 3, but the description adds practical meaning for names: they must match discovery_read listings, and ambiguous or missing names should be retried with an address. It also clarifies back behavior, though the mentioned act key is not present in the schema.

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?

The description states a specific verb and resource: it sets aside or restores communities/rivals discovered for the business, explicitly framed as 'Not for us'. It distinguishes itself from discovery_read by requiring the agent to read discovery first, though the opening phrasing is tangled.

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?

It gives a clear trigger: use when the owner says a community or rival is not theirs or not relevant. It also explains the prerequisite of reading discovery_read first and distinguishes back=true as restoration, though it does not explicitly enumerate when not to use the tool.

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

All Marsell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources