Skip to main content
Glama

get_market_structure_signal

Read-only

Use when assessing software category maturity, timing a market entry, or evaluating consolidation risk in a category. Returns market structure signal (consolidating or fragmenting) with citation evidence. Example: HR tech category — CONSOLIDATING signal, top 3 vendors hold 71% of AI citation share — late-stage consolidation signals pricing power shift to incumbents. Source: Stratalize market structure 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_market_structure_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a read-only, non-destructive, open-world call, so the safety bar is low. The description adds genuinely useful behavior the annotations cannot convey: the binary output shape, that results come with citation evidence, the underlying source (Stratalize composite), and a per-call price of $0.10 USDC.

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?

Usage conditions are front-loaded and the payoff/return description follows immediately. The example sentence is the longest element but earns its place by illustrating the signal output and implied category format; the source and price lines are terse and functional.

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 one-parameter read-only lookup with no output schema, the description covers trigger, return content (signal plus citation evidence), example output, provenance, and cost. The only material gap is that the output isn't structured into named fields, so the agent cannot anticipate exact payload shape.

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?

There is only one parameter and schema coverage is 0%, so the schema contributes nothing about the `category` string. The worked example implies the expected format (a named software category such as 'HR tech'), but this is inferred rather than stated, and there is no guidance on granularity or unrecognized categories.

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 the resource precisely — a 'market structure signal (consolidating or fragmenting)' — and states it returns citation evidence. That is specific enough to distinguish it from a generic market signal, though it never explicitly contrasts itself with siblings like get_macro_market_signal or get_category_disruption_signal.

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 three concrete use cases (assessing category maturity, timing market entry, evaluating consolidation risk), which is clear triggering context. It stops short of stating when not to use it or naming an alternative tool for overlapping questions, so the routing burden is partly on the agent's inference.

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