My Quant — Editorial Discovery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_capabilitiesA | Discover available product features, API/MCP URLs, versions, content limits, and interpretation boundaries before choosing a content tool. Returns product.capabilities.v1 metadata, without fetching stories or checking upstream freshness. Public and read-only; no credentials or arguments. Use latest_stories for recent records or get_health for endpoint compatibility. The mobile app distribution channel remains separately suspended. |
| get_healthA | Check that this endpoint responds with product.health.v1 metadata: product, API/MCP versions, deployed source SHA when available, and checked_at. Use for connection and version diagnosis; it does not fetch the editorial feed or prove source freshness. Public and read-only; no credentials or arguments. Use list_capabilities for supported surfaces and content limits. |
| latest_storiesA | 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. |
| get_storyA | Retrieve one published story using its exact stable ID from latest_stories or search_stories. Returns story, feed receipt, and release identity while retaining canonical sources, evidence clocks, publication state, release IDs, and limitations. Matching is exact and case-sensitive; an unknown ID returns a tool error. Public and read-only; no credentials. The canonical feed is cached for up to 60 seconds; unavailable or invalid feeds return a tool error. Use search_stories first when you only know a title or topic. |
| search_storiesA | Find published archive records by text when you do not know an exact story ID. All space-separated terms must match as case-insensitive substrings across IDs, titles, summaries, tags, products, beats, evidence status, contributions, or source labels/release IDs. Returns newest-first stories, normalized query, count, feed receipt, and release identity, preserving evidence clocks and limitations. No relevance ranking or pagination; zero matches returns an empty list. Public and read-only; no credentials. The feed is cached for up to 60 seconds; invalid queries or unavailable/invalid feeds return a tool error. Use get_story for an exact ID or latest_stories for an unfiltered overview. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct capability: metadata discovery (list_capabilities), health/version diagnosis (get_health), chronological listing (latest_stories), exact-ID retrieval (get_story), and text search (search_stories). The descriptions explicitly cross-reference sibling tools ('Use search_stories for...', 'Use get_story for an exact ID'), removing ambiguity between the two metadata tools and between listing vs. searching. An agent can reliably select the right tool for a given intent.
Most tools follow a predictable verb_noun snake_case pattern (list_capabilities, get_health, get_story, search_stories). The outlier is latest_stories, an adjective_noun phrase with no verb, which slightly breaks the pattern. Otherwise the convention is consistent and readable.
Five tools is well-scoped for a read-only editorial discovery surface, with each tool earning its place (capabilities, health, list, get, search). No redundant or trivially thin endpoints, and no bloat. The set is tight and purposeful.
The surface covers the core read-only discovery lifecycle: discover capabilities, verify health, list recent stories, fetch by ID, and search by text. Minor gaps remain, such as no pagination beyond 20 records and no tag/beat browsing distinct from free-text search, but agents can work around these. Coverage is solid for the stated public, read-only purpose.