Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Add rivals

add_rivals
Destructive

Adds who the business is up against, each with its website: direct (the same promise to the same buyers), adjacent (does one important part of the job) or substitute (what buyers do instead). They join the rival list Marsell's planner and Market read. The same name again changes that one.

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": {
      "rivals": "<rivals>"
    },
    "name": "add_rivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
rivalsYesOne or more rivals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the reason: 'The same name again changes that one' discloses upsert/overwrite behavior, which an agent would not learn from the flags alone. It stops short of saying whether an omitted field on re-add is cleared or preserved, which matters for a destructive write.

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?

Three short sentences, front-loaded with the verb and resource, then the categories, then the side effect. Slightly dense phrasing ('Adds who the business is up against') but nothing is wasted.

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 single-parameter mutation with no output schema and full annotation coverage, the description covers what it adds, the taxonomy, and the overwrite behavior. The only meaningful gap is the precise overwrite semantics on re-add, which is the one thing a destructiveHint write needs spelled out.

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 coverage is 100% and each nested field (url, kind, name, sells) is already described in the schema, including the same kind definitions the description repeats. The added value is limited to the array-level intent ('each with its website'), so baseline 3 applies.

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?

The description names a specific verb and resource ('Adds who the business is up against') and immediately scopes it with the three rival categories and the website field, which clearly separates it from the other add_* siblings (add_products, add_places, add_characters). An agent can tell what this tool creates 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 Guidelines3/5

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

It classifies the three kinds (direct/adjacent/substitute), which implicitly guides correct input, and it notes the downstream consumers ('Marsell's planner and Market read'). But it never says when to reach for this versus add_products or add_places, or when a competitor should be recorded as a product instead, leaving routing to inference.

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