Skip to main content
Glama

list_competitors

Read-only

Return competitor positioning entries (QuickBooks, Xero, FreshBooks, Wave, Zoho Books, Tally) with where HelloBooks wins, where the competitor wins, and pricing notes. Optional country, tier (primary / secondary), and id filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoReturn a single competitor by id (e.g. "quickbooks", "xero", "tally").
tierNoFilter to head-on rivals (primary) or adjacent / segment-specific overlaps (secondary).
countryNoOnly return competitors whose primary market is this country, or who are also evaluated in this market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. With no output schema, the description usefully discloses the shape of each returned entry (where HelloBooks wins, where the competitor wins, pricing notes) and the closed six-competitor universe, which tells the agent to expect a bounded, finite result set.

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?

Two sentences, front-loaded with the action and resource, then the filter options. The parenthetical competitor list is long but earns its place by communicating scope; the only mild redundancy is re-listing the three parameters already fully documented in the schema.

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 read-only, closed-world lookup with three optional enum-backed filters and annotations covering safety, the description supplies what's missing (returned fields, competitor coverage). No output schema exists, so explaining return content was the right call; only cross-tool routing to the compare_* siblings is absent.

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 description coverage is 100% — each parameter already has a description, and both enums are documented in the schema with meaning (primary=head-on rivals, secondary=adjacent overlaps). The description merely restates 'optional country, tier, and id filters' without adding syntax, default, or combination behavior, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Return') and resource ('competitor positioning entries'), and even enumerates the exact competitor set covered plus the three fields each entry carries (wins, competitor wins, pricing notes). The name is distinct from the list_* siblings, but the description never contrasts itself with closer tools like compare_books_to_hellobooks or compare_plans.

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?

Usage is only implied: 'Optional country, tier, and id filters' suggests this is a browsing/lookup tool with optional narrowing, but there is no explicit when-to-use vs. when-to-use-a-comparison-tool guidance and no stated preconditions. An agent can infer intent from the name and return fields, but nothing routes it away from the analyze/compare siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources