Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find competitors

find_competitors

Discover a brand's competitors, similar or adjacent companies from its domain, plus ad inspiration or company details by choosing competitors, inspiration, or company mode.

Instructions

Discover a brand's competitor / similar / adjacent brands from its domain (Claude grounded by web search). mode=competitors (default, excludes the searched company), inspiration (best relevant ads incl. it), or company. Bills the discovery model's token cost (no ad-data charge); free inside a new account's first-brand setup.

Input Schema

NameRequiredDescriptionDefault
modeNo'competitors' (default, excludes the searched company), 'inspiration' (best relevant ads incl. it), or 'company'
domainYesthe brand domain, e.g. flourish.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.161
    • changedInput schema / properties / domain / description
      Previous value: -"the brand domain, e.g. yourbrand.com"New value: +"the brand domain, e.g. flourish.com"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "candidates": {
-      "description": "discovered brands ({name, domain, kind, reason})",
-      "items": {},
-      "type": "array"
-    },
-    "diagnostics": {
-      "description": "discovery diagnostics (LLM tokens, web grounding)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds genuinely useful non-schema context: it bills the discovery model's token cost, carries no ad-data charge, and is free during a new account's first-brand setup. That complements the annotations (readOnly=false, openWorld=true, non-idempotent), while the web-search grounding signals nondeterminism. It stops short of describing result size or latency.

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 dense sentences with the core action front-loaded, followed by mode semantics and then cost implications. No redundant or filler text.

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 2-parameter tool with annotations and no output schema, the description covers action, modes, and billing, which is most of what an agent needs. The notable gap is that it never says what comes back (a list of brands, ads, etc.), which matters since no output schema exists.

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 the enum already documents each mode with the same wording used in the description, so the description adds no meaning beyond the schema. The domain parameter is only illustrated in the schema, not elaborated in the description.

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 ('Discover') plus the resource ('competitor / similar / adjacent brands from its domain') and names the grounding mechanism (Claude + web search). An agent can distinguish it from sibling discovery/analysis tools like competitor_teardown or pull_competitor_ads, which imply deeper analysis or ad retrieval.

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?

Explains the three modes and their differing behavior (default excludes the searched company; inspiration includes it and surfaces best relevant ads), which tells the agent which mode to pick. It does not explicitly contrast with sibling tools such as pull_competitor_ads or set_competitor_watch, so routing is clear but not fully exclusionary.

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