Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Search Signal8 Academy Guides

search_learn_guides
Read-only

Search Signal8 Academy guides to find plain-English explanations of dilution, SEC filings, market structure, and Signal8 usage, with titles, tracks, reading time, and links.

Instructions

Free: works without an API key or Pro plan (the hosted server only needs a signed-in account). Searches the Signal8 Academy (signal8.ai/learn): plain-English guides that explain dilution (ATMs, warrants, convertibles, baby shelf, cash runway), how to read SEC filings (8-K items, Form 4 codes, 13D/13G, 424B5, S-1/S-3), market structure (halts, short interest, float, reverse splits, STOCK Act disclosures) and how Signal8 works. Returns matching guides with title, description, track, section, reading time, lastVerified date, the public url and the signal8:// resource uri, without bodies. Keyword match: every query word must appear somewhere in the guide; title hits rank highest. An empty query lists every guide (optionally one track) in reading order. An empty result means no guide matched the words given (fewer or broader words match more guides, e.g. "warrant" rather than "warrant inducement repricing"), not that the topic is unimportant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_learn_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum guides to return (1-50, default 10).
queryNoWords to search for, e.g. "baby shelf", "form 4", "reverse split". Empty string lists every guide.
trackNoOptional. Restrict to one Academy track: "dilution" (dilution & toxic financing), "filings" (reading SEC filings), "market-structure" (halts, short interest, float, splits, congressional trading), or "signal8" (using Signal8, its API and this MCP server).

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this as a safe read-only search, and the description adds substantial behavior beyond them. It discloses free access, the signed-in-account requirement, returned fields without bodies, keyword matching behavior, title ranking, empty-query behavior, and the meaning of empty results.

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 description is front-loaded with the core function and access model, then moves into matching and result semantics. It is information-dense and mostly earns its length, though the long topic enumeration and parenthetical examples make it slightly heavier than necessary.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a complete input schema, useful annotations, and an output schema, and the description still covers access requirements, matching behavior, empty-query behavior, and return shape. Given that richness, an agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already complete, but the description adds real meaning beyond the schema by explaining that every query word must appear somewhere in the guide and that title hits rank highest. It also clarifies that an empty query lists every guide, optionally restricted to one track, in reading order.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it searches the Signal8 Academy's plain-English guides. It also scopes the content precisely, covering dilution, SEC filings, market structure, and Signal8 usage, which distinguishes it from sibling tools such as get_learn_guide or search_sec_filings.

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 description gives clear usage context: it is free, needs only a signed-in account, supports keyword search, and an empty query lists all guides in reading order. It explains matching semantics and what an empty result means, but it does not explicitly name the closest alternatives such as get_learn_guide or define_term.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools