Skip to main content
Glama

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

TDQS

A4/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, so the description is not carrying the safety burden. It goes beyond them usefully by disclosing the data provenance ('Stratalize market intelligence composite') and, importantly, a per-call cost of $0.10 USDC — a material behavioral fact an agent cannot get from structured fields. It does not state latency or limits, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the when-to-use clause, then the return payload, then a worked example, then provenance and price. Every sentence carries information, and the CRM example substitutes for the absent output schema without feeling padded.

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, yet the description conveys the return shape (growth signal, citation leaders with share percentages, disruption risk level) and demonstrates it concretely with the CRM walkthrough. Combined with cost and data source, the main gaps are only input-format specifics and output field naming.

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?

With one parameter at 0% schema description coverage, the description must supply the meaning of 'category'. 'Software category' plus the CRM example conveys that the value is a market category label, but it gives no format, casing, taxonomy, or list-of-valid-values guidance, so an agent still has to guess at valid input strings.

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 'growth signal, AI citation leaders, and disruption risk for any software category', scoped to SaaS category assessment. That is clearly distinct from neighbors like get_saas_metrics_benchmark or get_software_pricing_intelligence in substance, but the description never names a sibling or explicitly delimits itself, so differentiation is inferred rather than stated.

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 condition ('Use when assessing a SaaS category investment thesis, competitive dynamics, or market momentum before a strategic decision'), which gives a clear decision context. It stops short of exclusions or naming an alternative tool for adjacent needs, so there is no when-not guidance.

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