Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find competitors

find_competitors

Discover a brand's competitors, similar, or adjacent brands from a domain. Choose competitor, ad 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. Costs a few credits for the discovery model (no ad-data charge); free inside a new account's first-brand setup.

Input Schema

TableJSON 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.1/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, destructive hints, and the description adds important behavioral cost structure ('Costs a few credits for the discovery model (no ad-data charge); free inside a new account's first-brand setup') which the agent needs for planning. It also discloses the grounding mechanism ('Claude grounded by web search'). It stops short of describing return format or rate limits, but the credit model is valuable non-structured context.

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?

It's a single dense sentence but front-loads the core action and mode distinctions before the cost note. Slightly packed, but every clause earns its place by covering purpose, modes, and billing.

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 discovery tool with no output schema and only two params, the description covers purpose, mode selection, grounding source, and the credit/free-first-brand nuance. The main gap is not describing the shape of the returned competitor list, though that's a minor omission given the task is exploratory discovery.

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%, so both parameters including the mode enum are fully documented in the schema itself. The description restates the mode options but adds no syntax, format, or validation detail beyond what the schema provides, so the baseline of 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 states a specific verb and resource ('Discover a brand's competitor / similar / adjacent brands from its domain') and distinguishes the three modes with their distinct outputs, so an agent can tell it apart from siblings like search_meta_ads or pull_competitor_ads 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?

It specifies which mode to use ('competitors' default excludes the searched company; 'inspiration' includes it; 'company'), giving practical selection guidance. However it doesn't state when to use this tool versus sibling alternatives like find_creators or competitor_teardown, so it stops short of full when/when-not guidance.

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