Skip to main content
Glama

Stratalize Intelligence

Get Market Intelligence Brief

get_market_intelligence_brief
Read-only

Use when producing a quick industry intelligence brief or validating market narrative for a strategy deck. Returns AI-generated market summary, up to six key themes, and sentiment skew for any industry. Example: Healthcare IT market — POSITIVE sentiment 68%, key themes: EHR consolidation, AI-assisted coding, value-based care expansion — consolidation narrative dominant across 847 analyzed queries. Source: Stratalize AI citation composite. $0.50 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": {
      "industry": "<industry>"
    },
    "name": "get_market_intelligence_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
industryYes

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 establish read-only, non-destructive, open-world behavior, and the description adds materially: the output shape (summary, up to six themes, sentiment skew), the provenance ('Stratalize AI citation composite'), and a per-call price of $0.50 USDC. Pricing and sourcing are exactly the kind of cost/auth context annotations cannot carry. It stops short of stating rate limits or failure behavior.

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 trigger condition and the return contents are front-loaded in the first two sentences, with the worked example and pricing following. The example is long but demonstrates the output format usefully; it is close to, but not over, the point of excess.

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?

There is no output schema, so the description must describe returns and it does so concretely. For a 2-parameter read tool the only real gap is the undocumented 'topic' parameter and any note on whether results vary by query volume or freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It hints that 'industry' is a free-form industry string ('for any industry'), but the optional 'topic' parameter is never mentioned at all, leaving an agent to guess what it scopes or how it interacts with industry.

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 verb and resource ('Returns AI-generated market summary, up to six key themes, and sentiment skew') and scopes it with 'for any industry'. That scoping implicitly separates it from the vertical-specific siblings (get_provider_market_intelligence, get_saas_market_intelligence, etc.), though no sibling is named explicitly.

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?

It gives clear when-to-use triggers: 'producing a quick industry intelligence brief or validating market narrative for a strategy deck'. There are no when-not conditions and no named alternatives for narrower vertical lookups, which keeps it short of a 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