Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find competitors

find_competitors
Read-only

Discover competitor, similar, or adjacent brands from any domain. Choose modes for competitors, inspiration, or company insights.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds valuable behavioral context: it is grounded by web search, costs a few credits for the discovery model (no ad-data charge), and is free inside a new account's first-brand setup. This goes beyond the annotations and clarifies the tool's execution characteristics. No contradiction with annotations.

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 two sentences, front-loading the core purpose and then providing mode details and cost. Every sentence serves a purpose, with no redundancy or fluff. It is well-structured and easily scannable.

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 tool with only two parameters, no output schema, and read-only annotations, the description is largely complete. It explains the modes and cost, but does not elaborate on what the 'company' mode specifically returns or any limitations like pagination. However, given the simplicity and that the schema covers parameter syntax, the missing return details are minor. The description adequately equips an agent to call it correctly.

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 schema already documents both parameters. The description enriches the 'mode' parameter by explaining each enum value's behavior ('competitors' excludes the searched company, 'inspiration' includes best relevant ads). It also clarifies the domain parameter implicitly through examples. This adds meaning beyond the schema's generic descriptions.

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 clearly states the tool's purpose: discovering a brand's competitor/similar/adjacent brands from its domain, grounded by web search. It specifies the resource (domain) and the action (discover competitors), and differentiates itself from sibling tools like competitor_teardown and pull_competitor_ads by focusing on the discovery of similar brands. The description is specific and not a tautology.

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 usage context by explaining the three modes (competitors, inspiration, company) and their behaviors, including the default mode and whether the searched company is included. It also notes cost implications and a free condition for new accounts, which helps the agent decide when to use this tool. However, it does not explicitly contrast with alternatives like competitor_teardown or search_google_ads, so it lacks explicit exclusions.

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