Skip to main content
Glama
Sign In
Marketic

Marketic

by Das-rebel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

compare_competitors

Compare your product against competitors to obtain a feature matrix, price comparison, and strategic recommendations for informed decision-making.

Instructions

Compare your product against multiple competitors. Returns feature comparison matrix, price comparison, and strategic recommendations.

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": {
      "your_product": "<your_product>",
      "competitors": "<competitors>"
    },
    "name": "compare_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorsYes
your_productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.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 full burden of disclosing behavior. It does state that the tool 'Returns feature comparison matrix, price comparison, and strategic recommendations,' which is good, but it does not explicitly state read-only nature or absence of side effects. For an analysis tool this is acceptable, but not fully transparent.

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?

The description is a single, efficient sentence that front-loads the purpose and then lists the outputs. There is no wasted text, making it easy to parse quickly.

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 simple tool with two parameters and no output schema, the description covers the primary purpose and output types. However, it does not mention potential error conditions, input format expectations, or any special prerequisites, leaving minor gaps for an agent that needs to call it correctly.

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 description coverage is 0%, meaning the description does not explain the parameters beyond what the schema names. It mentions 'your product' and 'multiple competitors' but does not elaborate on formats, constraints, or examples. The description fails to compensate for the low schema coverage, so an agent gets little extra semantic clarity.

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 states a clear verb ('Compare') and resource ('your product against multiple competitors'), and specifies the output types. The phrase 'multiple competitors' distinguishes it from sibling tools like 'analyze_competitor' which likely handle single competitors, so an agent can tell them apart 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?

The description provides clear context: it is for comparing against multiple competitors, which implicitly guides selection over single-competitor tools. However, it does not explicitly mention alternatives or when not to use it, so it lacks exclusions but is clear enough for typical use.

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

Deploy Server

Other Tools