SplitScanner

Get Signal8 Academy Guide

get_learn_guide

Read-only

Free: works without an API key or Pro plan (the hosted server only needs a signed-in account). One Signal8 Academy guide as Markdown, by track and slug (as returned by the Academy search, or from a signal8.ai/learn// URL). Returns title, description, section, lastVerified, the public url, the full Markdown body (links already rewritten to absolute signal8.ai URLs), the related guides, the glossary terms it uses (with one-line definitions) and its SEC sources (accession numbers). Guides use hypothetical examples ("Company X") unless a source is cited; they are education, not advice about any named company, and each guide's url is its citable source.

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": {
      "track": "<track>",
      "slug": "<slug>"
    },
    "name": "get_learn_guide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Guide slug (kebab-case), e.g. "what-is-dilution", "s1-vs-s3-baby-shelf", "form-4-codes".
`track`	Yes	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

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/non-destructive annotations: it discloses the no-API-key access requirement, that links are rewritten to absolute URLs, that guides use hypothetical examples unless sourced, and that the guide's url is the citable source. That is exactly the kind of auth, transformation, and attribution context annotations cannot carry.

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-loads the two things an agent needs first — free access and the retrieval contract — then enumerates returns in a single clause. The return enumeration overlaps somewhat with the output schema, but it is compact and no sentence is filler.

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?

With annotations covering safety and an output schema covering return shape, the description fills the remaining gaps: access tier, input provenance, link rewriting, and citation/advice disclaimer. Nothing an agent needs to call this correctly is missing.

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 100%, so the schema already carries both parameters, making 3 the baseline. The description adds real meaning by mapping the slug to the signal8.ai/learn/<track>/<slug> URL form, which helps the agent derive valid inputs from a link rather than only from search results.

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?

States a specific verb and resource — 'One Signal8 Academy guide as Markdown, by track and slug' — and immediately scopes it against the search sibling by noting slugs come 'as returned by the Academy search'. An agent can distinguish this from search_learn_guides without opening either schema.

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?

Gives clear context for when this applies (retrieving a single known guide) and tells the agent where the key inputs come from: the Academy search results or a signal8.ai/learn/<track>/<slug> URL. It does not explicitly say to use search_learn_guides when the slug is unknown, so the alternative routing is implied rather than stated.

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

All SplitScanner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.