Skip to main content
Glama

Stratalize Intelligence

Get Category Ai Leaders

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), but the description adds material context beyond them: the underlying data source (Stratalize AI citation index), a per-call price of $0.10 USDC, and the fact that ranking is by unprompted mentions rather than prompted ones. It still omits behavior for unknown or unmatched categories and any pagination or result-size limits.

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?

Usage context is front-loaded, followed by return shape, a worked example, provenance, and price — a sensible order with no filler sentences. The numeric example is useful but slightly verbose in its second half ('dominates AI recommendations by 50% over nearest competitor'), which restates the ranking data.

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 correctly supplies the return shape (vendors ranked by mention frequency) and an illustrative payload. Combined with cost and source disclosure, an agent has nearly everything needed for a one-parameter read tool; only taxonomy/format guidance for the category argument is missing.

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?

There is a single parameter, 'category', with 0% schema description coverage, so the description carries the burden. The CRM example implicitly signals that the value is a free-text software category label, but it never states whether the string must match an internal taxonomy, whether casing or synonyms matter, or what happens on a miss.

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 and resource: returns vendors ranked by unprompted AI mention frequency for a software category, framed by the research question it answers (AI brand visibility). It does not, however, differentiate itself from plausible siblings such as get_top_vendors_by_category or get_brand_momentum, so an agent must still infer which to pick.

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 concrete use context that an agent can match against a request. There are no explicit exclusions and no named alternative for the adjacent vendor-ranking tools, which keeps it below 5.

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