Skip to main content
Glama

storyflo

by com.storyflo.api

Unified search (news + declassified + signals)

search_unified
Read-onlyIdempotent

Search ALL of Storyflo in one call and get results back as separate per-corpus buckets: news (the narrated article archive), declassified (government-document cases), and signals (Atlas's book of positions off the Divergence Index). Use this when you do not already know which corpus holds the answer, or when a topic spans several — e.g. a macro question with both coverage and a live position. Results are ranked WITHIN each corpus and never blended, so a large corpus cannot drown a small one. profile=desk leads with signals (news/declassified as supporting evidence); profile=publisher leads with news and declassified carrying attribution for citation. Signals are qualitative only — no raw market odds, not investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results PER CORPUS.
queryYesWhat to search for, across every corpus.
corporaNoComma-separated subset: news, declassified, signals. Omit for all three.
profileNoRanking emphasis. Same buckets either way; only order and enrichment differ.
verticalNo

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that results are never blended across corpora, are ranked within each corpus, and that profile changes ordering/enrichment—plus the qualitative-only nature of signals. This adds meaningful behavioral context.

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?

The description is a single, well-organized paragraph that front-loads purpose ('Search ALL of Storyflo') and packs each sentence with distinct information—corpora definitions, use case, ranking behavior, profile effects, and caveat.

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?

For a read-only search with no output schema, it explains result structure (per-corpus buckets), ranking, profile impact, and the qualitative limitation of signals. The only significant gap is the undocumented 'vertical' parameter.

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 already covers 4 of 5 parameters with descriptions; the description adds semantic value for 'profile' (desk vs publisher) and explains corpora buckets, though 'vertical' remains undocumented.

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?

Explicitly states 'Search ALL of Storyflo in one call' and names the three corpora (news, declassified, signals), distinguishing it from sibling search tools by the unified scope and per-corpus bucketing.

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?

Provides explicit usage guidance: 'Use this when you do not already know which corpus holds the answer, or when a topic spans several,' clearly indicating when the unified search is appropriate over narrower alternatives.

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

All storyflo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is overlap between `get_my_private_feed`, `subscribe_topic`, and `list_subscriptions`—all return or manage feed URLs, which could confuse an agent. Otherwise, categories like publisher, fund manager, and search tools are clearly separated.

Naming Consistency5/5

All tools use consistent snake_case with a verb_noun pattern (e.g., `get_article`, `search_articles`, `publisher_upload_audio`). Exceptions like `digest` are single-word verbs but still fit the pattern. No mixed conventions are present.

Tool Count2/5

With 37 tools, the server exceeds the 25-tool threshold considered 'too many' by the rubric. While the broad scope (news, podcasting, publishing, fund management, embedding) justifies a large surface, the count still adds cognitive load and would benefit from splitting into separate servers.

Completeness4/5

The tool set covers the major domains: search, retrieval, subscriptions, publishing, fund manager operations, and embedder network. Minor gaps exist, such as the absence of an unsubscribe or delete-episode tool, but the core workflows are well-supported and agents can accomplish most tasks.

Resources