My Quant — Editorial Discovery

by beepboop2025

Overview Schema Source Related Servers Discussions Admin

Read the latest evidence-bounded stories

latest_stories

Read-onlyIdempotent

Retrieve recent published archive records for a chronological overview when no search term is needed. Returns count, stories, feed receipt, release identity, and evidence details.

Instructions

Read recent published archive records when you want a chronological overview without a search term. Returns count, stories, the feed receipt, and release identity; each story retains sources, evidence clocks, publication state, release IDs, and limitations. Public and read-only; no credentials. Lists default to 10 records, at most 20, without pagination. The canonical feed is cached for up to 60 seconds; unavailable or invalid feeds return a tool error. Use search_stories for text matching or get_story for an exact returned ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum records to return, newest first; 1–20, default 10. There is no pagination parameter.

Output Schema

TableJSON Schema

Name	Required	Description
`feed`	Yes	Canonical feed URL, content hash, item count, publication authority, and retrieval timestamp.
`count`	Yes	Number of records returned, not the total number of matches.
`schema`	Yes
`release`	Yes	MCP version and deployed source SHA, when available.
`stories`	Yes	Newest-first published records retaining stable IDs, source links, evidence clocks, publication state, release IDs, and limitations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Oct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior; the description adds meaningful context beyond that: public access with no credentials, default/maximum limits, no pagination, 60-second caching, and error behavior for unavailable or invalid feeds. No contradiction with annotations exists.

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 dense but every sentence carries information: primary purpose, return contents, access model, limits, caching, error behavior, and alternatives. It is front-loaded with the core usage and does not waste words.

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?

Given the single optional parameter, rich annotations, output schema, and sibling tooling, the description covers everything needed to invoke the tool correctly: input limits, output contents, safety profile, error cases, and when to choose a different tool. Nothing important is missing.

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?

The only parameter, limit, is fully documented in the schema with default, minimum, maximum, and no-pagination semantics. The description repeats the default/maximum behavior without adding substantial new meaning beyond the schema, so the baseline of 3 is appropriate.

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 ('Read'), a clear resource ('recent published archive records'), and a clear use case ('chronological overview without a search term'). It explicitly distinguishes itself from siblings by naming search_stories and get_story as alternatives for other needs.

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?

The description gives explicit when-to-use guidance: use this when you want chronology without a search term. It also names search_stories for text matching and get_story for exact IDs, which clearly routes an agent away from this tool when those conditions apply.

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

Deploy Server