Skip to main content
Glama

Stratalize Intelligence

Get Saas Market Intelligence

get_saas_market_intelligence
Read-only

Use when assessing a SaaS category investment thesis, competitive dynamics, or market momentum before a strategic decision. Returns growth signal, AI citation leaders, and disruption risk for any software category. Example: CRM category — GROWING signal, Salesforce leads at 42% citation share, HubSpot gaining 8% share year-over-year, disruption risk MODERATE from AI-native CRMs — signals consolidation pressure on mid-tier vendors. Source: Stratalize market intelligence 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": {
      "category": "<category>"
    },
    "name": "get_saas_market_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 genuine value with the composite data source and the $0.10 USDC per-call cost, which an agent needs for budget decisions, but says nothing about latency, caching, rate limits, or failure modes.

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?

Well front-loaded: trigger first, then returned fields, then an illustrative example, then source and price. The CRM walkthrough is the longest block and is mostly justified as a format demonstration, though it could be a sentence shorter without losing meaning.

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 must convey return content and does so through the stated signal/citation-leader/disruption-risk fields plus a concrete example. Cost and provenance are covered; the remaining gap is the exact response shape and citation-share units, which an agent would discover only after paying.

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?

Only one parameter, 'category', with 0% schema description coverage, so the description has to carry the load. It partially does via the worked example 'CRM category', which implies free-text category naming, but it never states accepted granularity, casing, or what happens with an unrecognized category.

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 capability: returns growth signal, AI citation leaders, and disruption risk for any software category. That is concrete enough for an agent to know what comes back, but it never distinguishes itself from near-neighbours such as get_saas_metrics_benchmark or get_market_intelligence_brief.

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 trigger: 'Use when assessing a SaaS category investment thesis, competitive dynamics, or market momentum before a strategic decision.' That gives clear situational context, but there is no when-not-to-use clause and no named alternative for adjacent questions like pricing or benchmarks.

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