Skip to main content
Glama

Stratalize Healthcare

Get Investment Category Signal

get_investment_category_signal
Read-only

Use when evaluating VC software category attractiveness or assessing portfolio category exposure before an investment decision. Returns growth signal, top brands, and citation evidence for any software category. Example: AI infrastructure category — GROWTH signal, top brands Nvidia 67% citation share, Anthropic 18%, xAI 9% — accelerating citation growth signals sustained investment thesis. Source: Stratalize citation heuristics. $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_investment_category_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the data source (Stratalize citation heuristics) and a per-call cost of $0.10 USDC, which matters for an agent deciding whether to call repeatedly. It does not say what happens when a category is unknown or unmatched, which is a real gap for an open-world lookup.

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 usage trigger, then return contents, then a worked example, then source and price. The AI-infrastructure example earns its space because there is no output schema and it demonstrates the return shape (signals, share-of-citation percentages, trend direction).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does a fair job describing return contents via the worked example, and it discloses source and pricing. However, for an open-world paid lookup it omits coverage limits (which categories exist), failure/empty-result behavior, and how the growth signal is scaled or interpreted beyond the single 'accelerating' example.

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% for the single required parameter, so the description carries the full burden and mostly fails: it says 'any software category' and shows one illustrative value ('AI infrastructure category') but never specifies acceptable naming (free text vs slug vs taxonomy term), casing, or fallback behavior for unmatched 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?

States a specific verb and resource: retrieves growth signal, top brands, and citation evidence for a software category, with the intended decision context (VC category attractiveness, portfolio exposure). It is clear what the tool returns, but it never distinguishes itself from near-identical siblings such as get_category_disruption_signal or get_competitive_displacement_signal, so an agent must guess which category signal to pick.

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?

The opening clause gives an explicit when-to-use condition (evaluating category attractiveness, assessing portfolio exposure before an investment decision). It stops short of naming alternatives or stating when NOT to use it, so routing among the many sibling signal tools is left to 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