Skip to main content
Glama

Stratalize Intelligence

Get Sector Ai Intelligence

get_sector_ai_intelligence
Read-only

Use when producing equity research, tracking brand share in AI sector coverage, or benchmarking a company AI visibility against sector peers. Returns top brands by AI mention share, sector trend narrative, and themed bullets for any equity sector. Example: Financials sector — JPMorgan leads at 34% citation share, Goldman 22%, BlackRock 18% — narrative focused on digital transformation and cost efficiency. Source: Stratalize AI citation composite. $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": {
      "sector": "<sector>"
    },
    "name": "get_sector_ai_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the upstream source (Stratalize AI citation composite) and a per-call price of $0.10 USDC, which matters for an agent deciding whether to call it. It stops short of disclosing data freshness, coverage limits, or latency.

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 structure is well front-loaded: use-case triggers first, then return contents, then a worked example, then source and price. Every sentence contributes, though the inline percentage example is slightly long for what it conveys and the title merely restates the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-required-parameter tool with no output schema, the description does what an agent needs: it states the triggering scenarios, enumerates the returned artifacts, illustrates the shape of a result, and discloses source and cost. The only residual gap, sector taxonomy, is minor and largely covered by the example.

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 0% and the single `sector` parameter is an unconstrained string, so the description carries the burden of explaining valid values. It only weakly compensates, hinting at the format through the example "Financials sector" without stating an accepted taxonomy (GICS vs. free text, casing, valid enumeration), leaving real ambiguity about what strings will resolve.

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 names a specific resource (equity sector AI intelligence) and enumerates the concrete payload: top brands by AI mention share, sector trend narrative, and themed bullets. It is clearly distinct from compliance-oriented siblings like get_eu_ai_act_coverage or labor siblings like get_bls_sector_employment, though it never explicitly names the nearest alternative such as get_category_ai_leaders.

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 producing equity research, tracking brand share in AI sector coverage, or benchmarking a company AI visibility against sector peers" gives three concrete triggering scenarios. There is no when-not guidance and no named alternative tool, so the agent must infer the boundary against get_category_ai_leaders and get_market_intelligence_brief itself.

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