Skip to main content
Glama

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. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/non-destructive annotations, it discloses two valuable traits: the output is AI-generated (so treat as synthesized narrative, not primary data) and each call costs '$0.50 USDC'. The stated source and '847 analyzed queries' scale hint adds provenance. It does not cover latency, rate limits, or failure behavior, so not 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?

Front-loaded with the when-to-use clause, then return contents, then a worked example. The Healthcare IT example is long but earns its place by conveying output shape where no output schema exists; the pricing and source sentences are short and material.

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 two-parameter, no-output-schema tool, the description compensates well by describing the return payload (summary, up to six themes, sentiment skew) via a concrete example and by disclosing cost. The main remaining gap is the unexplained optional 'topic' parameter.

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% with two parameters, so the description carries the full burden. 'For any industry' loosely clarifies the required industry field, but the optional 'topic' parameter is never mentioned, leaving half the input surface undocumented.

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?

Specific verb-and-resource phrasing: returns an 'AI-generated market summary, up to six key themes, and sentiment skew' for a named industry. The 'for any industry' scope implicitly separates it from the many vertical-named siblings (get_provider_market_intelligence, get_saas_market_intelligence), though no sibling is named directly for contrast.

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?

Opens with an explicit triggering condition: 'Use when producing a quick industry intelligence brief or validating market narrative for a strategy deck.' That gives a clear situational context, but there are no exclusions or named alternatives for when a vertical-specific intelligence tool would be a better fit.

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