Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Filing Sentences by Theme

get_sentences
Read-onlyIdempotent

Retrieve the actual sentence text from SEC filings that triggered a classifier. Use this after screening to see exactly what language caused a signal to fire. Requires a classifier name plus either a ticker or accession number. Returns the matching sentences ranked by classifier score (highest first). Use search_classifiers first to find valid classifier names.

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": {
      "classifier": "<classifier>"
    },
    "name": "get_sentences"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sentences to return (default: 20, max: 50)
tickerNoFilter to a specific company ticker (e.g. 'AAPL').
classifierYesClassifier name to get sentence hits for (e.g. 'is_pricing_power_expanding'). Use search_classifiers to discover names.
filed_beforeNoRestrict to sentences whose filing_date <= this YYYY-MM-DD (point-in-time replay cutoff).
accession_numberNoFilter to a specific filing accession number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavior the annotations don't: results are ranked by classifier score, highest first, and the required input combination. It stops short of describing truncation or what happens when no sentences match.

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?

Four short sentences, front-loaded with the action and followed by sequencing, input requirements and return-order. No filler and no repetition of the title.

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?

For a five-parameter read-only lookup with no output schema, the description covers what is returned, how it is ordered, and how to obtain a valid classifier name. Nothing an agent needs in order to call it 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 baseline is 3, but the description adds a constraint the schema does not encode: a classifier name plus 'either a ticker or accession number.' That either/or targeting rule is real added meaning beyond the field docs, which describe both filters as optional.

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 opens with a specific verb and resource: 'Retrieve the actual sentence text from SEC filings that triggered a classifier.' It scopes the result to classifier-triggered sentences, which distinguishes it from a generic filing-text tool like get_filing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the workflow position ('Use this after screening to see exactly what language caused a signal to fire') and an explicit prerequisite ('Use search_classifiers first to find valid classifier names'), naming the sibling to call before this one.

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