Skip to main content
Glama

get_category_ai_leaders

Read-only

Use when assessing brand visibility in AI-generated recommendations or researching which vendors dominate AI platform responses in a software category. Returns vendors ranked by unprompted AI mention frequency. Example: CRM category — Salesforce 42 mentions across 100 queries, HubSpot 28, Microsoft Dynamics 14 — Salesforce dominates AI recommendations by 50% over nearest competitor. Source: Stratalize AI citation index. $0.10 USDC per call.

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": {
      "category": "<category>"
    },
    "name": "get_category_ai_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), yet the description still adds genuinely new information: the data source (Stratalize AI citation index), the cost ($0.10 USDC per call), and the 'unprompted' mention methodology that defines the metric. It does not discuss latency or rate limits, which keeps it from a 5.

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?

The when-to-use clause is front-loaded, followed by return semantics, a concrete example, provenance, and price — each sentence adds a distinct fact. The numerical example is somewhat verbose but earns its place by showing both the output shape and the interpretation.

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?

With no output schema, the description carries the burden of explaining returns, and it does so: ranked vendors, mention counts over a query base, and what the ranking means. For a one-parameter read-only tool it is nearly complete, with only category input conventions left unaddressed.

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 0%, so the single 'category' string parameter is undocumented in structured form; the description compensates by clarifying that it means a software category and giving 'CRM category' as a worked example with realistic output. It still doesn't specify accepted category naming conventions or how granular a category can be, which limits it to a 4.

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?

The description states a specific verb and resource — 'Returns vendors ranked by unprompted AI mention frequency' for a software category — which is far more concrete than the bare tool name. It implicitly distinguishes itself from general vendor-ranking tools by emphasizing AI-generated recommendation context, but it never names a sibling (e.g. get_top_vendors_by_category) to make the boundary explicit.

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 opening 'Use when assessing brand visibility in AI-generated recommendations or researching which vendors dominate AI platform responses' gives a clear triggering context, reinforced by a concrete CRM example. It stops short of stating when NOT to use it or which sibling to prefer for adjacent questions, so it lands at clear-context-without-exclusions.

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