Skip to main content
Glama
Sign In

BotSpot: AI Trading, Backtests and Bots

by io.github.grzesir
OverviewDiscussionsAdmin

Search public research documents

search_documents
Read-onlyIdempotent

Search public research documents, initially SEC EDGAR filings. Use this to find 10-K, 10-Q, 8-K, S-1, DEF 14A, Form 4, and 13F-HR documents before calling get_document. Use datasetId sec.full_text_search with query when searching across EDGAR text without a specific company.

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_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoHistorical availability ceiling, preferably a timezone-aware ISO timestamp. Calendar-period selection alone is not publication-time or original-vintage replay. Release archives and SEC documents support disclosed historical approximations; some current-only sources cannot return historical evidence.
limitNo
queryNo
entityNoTicker, CIK, company name, or manager name. Optional for SEC full-text search.
datasetIdNoRegistered document dataset id from discovery, such as sec.filings, sec.filing_sections, sec.current_filings, or sec.full_text_search.
timeRangeNo
documentTypesNoSEC form filters such as 10-K, 10-Q, 8-K, S-1, DEF 14A, 13F-HR, 4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asOf / description
      Previous value: -"Historical availability ceiling, preferably a timezone-aware ISO timestamp. Calendar-period selection alone is not publication-time or original-vintage replay. Unqualified source history returns unsupported_capability."New value: +"Historical availability ceiling, preferably a timezone-aware ISO timestamp. Calendar-period selection alone is not publication-time or original-vintage replay. Release archives and SEC documents support disclosed historical approximations; some current-only sources cannot return historical evidence."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful non-annotation context: the dataset is expandable ('initially SEC EDGAR') and results are meant to feed get_document. It says nothing about ranking, result volume, or pagination/limit behavior, which is a meaningful omission for a search tool.

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?

Three sentences, all front-loaded with the highest-value information (what it searches, workflow position, dataset mode). No filler or restated boilerplate. The third sentence is dense but earns its place by giving an exact datasetId value.

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 7 optional parameters, a nested timeRange object, no required fields, and no output schema, the description should do more than it does. It never explains how timeRange/asOf interact with historical replay, nor what a result contains or how to page through it, which leaves an agent guessing on a fairly complex tool.

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?

Schema coverage is 57%, and the description only adds meaning for two parameters: query and datasetId (with the concrete value sec.full_text_search, plus the implication that entity is optional for full-text search). The complex parameters asOf, timeRange, and limit are left entirely to the schema, including the non-obvious historical-vintage semantics of asOf.

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 and resource plus a concrete scope ('public research documents, initially SEC EDGAR filings') and enumerates the covered form types (10-K, 10-Q, 8-K, S-1, DEF 14A, Form 4, 13F-HR). It also positions the tool relative to get_document. It does not distinguish itself from the other search_* siblings (e.g., search_data_catalog), which is the only real gap.

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 ('Use this to find ... before calling get_document') and gives a conditional routing rule: use datasetId sec.full_text_search with query when searching EDGAR text without a specific company. No explicit when-not-to-use or named alternatives for the non-EDGAR case.

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

All BotSpot: AI Trading, Backtests and Bots toolsInspect
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.

Resources