Skip to main content
Glama

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

TDQS

A3.9/5.0
Behavior4/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 safety is covered. The description adds genuinely new context: what the response contains, that it derives from Stratalize citation heuristics, and notably a $0.10 USDC per call cost, which is critical for an agent deciding whether to invoke. It does not cover pagination, coverage limits, or failure behavior for unknown categories.

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?

The usage condition is front-loaded, followed by return contents, a compact example, provenance, and price. Every element serves a purpose, though the example's detailed percentages are somewhat verbose relative to the one-line schema.

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 carries the burden of describing returns, and it does so adequately: growth signal, top brands with citation shares, and citation evidence, reinforced by an example. Combined with the cost disclosure and provenance, an agent has what it needs to call it, with only category-string format and error behavior left ambiguous.

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 a single parameter, 'category', with 0% schema description coverage, so the schema contributes nothing about format. The description partially compensates by scoping it to 'any software category' and showing an example ('AI infrastructure category'). It still leaves open whether the value must match a canonical category name, how granular it can be, and what happens on a miss.

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 gives a specific verb+resource: returns a growth signal, top brands, and citation evidence for a software category. The concrete example (AI infrastructure, Nvidia 67% citation share) makes the output tangible. It does not explicitly distinguish itself from near siblings like get_category_disruption_signal or get_category_ai_leaders, which keeps it below a 5.

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 states a clear usage context: evaluating VC software category attractiveness or portfolio category exposure before an investment decision. That is a real when-to-use condition rather than an implied one. There is no when-not guidance and no named alternative for adjacent signals, so it stops short of a 5.

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