Skip to main content
Glama

Seiche — world-markets evidence terminal

by io.github.beepboop2025

Seiche World Markets: money, FX, macro-capital and China evidence

world_markets_context
Read-onlyIdempotent

Unified, chartless context for broad financial-market questions. It projects only completed/public state into money_markets, forex, macro-capital transmission, China macro evidence, official references, methodology, or a compact summary. Every response carries snapshot/as-of clocks, canonical Seiche citation URLs, and explicit observed, derived, structural, restricted, and unavailable boundaries. The China structural catalog is unsigned; only status=restricted represents a verified Seiche owner-attested revision; both states keep NBS values, raw evidence, and history withheld. A separately operator-accepted economic_context may publish licensed World Bank WDI values with annual/structural freshness, distinct release, Palimpsest collection, and Seiche acceptance clocks. Those values are context only and never a live print, score, gauge, forecast, or signal. The sources selector is reference-only; use all when verified China context and its NBS source linkage must appear together. Coverage is curated and partial rather than exhaustive or uniformly live. It never triggers collection, repository history reads, or model fitting. Its named-field whitelist omits chart and history arrays for data minimization; that is not a per-record licensing audit. Capital coverage is limited to public positioning proxies, Treasury primary-market absorption, market stress, official liquidity and global dollar credit—not a security master, issuer-data service or consolidated tape. Use Undertow instead when the question is specifically about executable depth, liquidity-provider concentration, or position-sized exit cost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoProjection to return; defaults to the compact cross-market summary.summary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
as_ofNo
forexNo
scopeNo
clocksNo
reasonNo
schemaNo
statusNo
sourcesNo
summaryNo
categoryNo
citationNo
coverageNo
selectionNo
disclaimerNo
china_macroNoMetadata-only NBS catalog. Structural is an unsigned code-owned catalog; restricted means a Seiche owner-attested revision was verified. A separate optional economic_context contains only operator-accepted annual World Bank WDI observations and remains ineligible for scores and gauges.
methodologyNo
context_onlyNo
generated_atNo
money_marketsNo
canonical_urlsNo
capital_marketsNo
status_definitionsNo
available_selectorsNo
chart_history_includedNo

TDQS

A4.3/5.0
Behavior5/5

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

The description is unusually rich in behavioral disclosure: it states what the tool never triggers (collection, repository history reads, model fitting), what the data boundaries are (curated, partial, not a security master or consolidated tape), the copyright status of China catalog entries, freshness clauses, and exact boundary types ('observed, derived, structural, restricted, unavailable'). This adds substantial context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and long, with many stacked clauses and some jargon (e.g., 'advanced timestamp', 'Palimpsest collection', 'named-field whitelist excludes chart/history arrays'). In one pass it is hard to grasp the main action and the key use conditions. The core guidance could be front-loaded in two or three sentences, with the remaining details in a shorter, structured form. This is not concise enough for an agent to quickly parse and act on.

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 single-parameter, read-only, idempotent tool with a rich output schema, this description is extremely comprehensive. It defines the exact coverage, the boundary of what data is and isn't included, the relationship to a sibling, and the semantics of the only parameter. An agent has everything needed to select and call it correctly.

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 description coverage is 100% (the 'section' parameter is fully documented), so the baseline credit applies. The description further adds meaning by explaining the semantics of 'use all when verified China context and its NBS source linkage must appear together' and clarifying that 'sources' is reference-only. This is meaningful beyond the schema, so a 4 is warranted.

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 identifies a specific verb ('Unified... context') and a clear resource: it returns financial-market context across sections like money_markets, forex, macro-capital transmission, and China evidence. It explicitly distinguishes itself from the sibling Undertow for executable depth, which helps an agent know what this tool is not. However, the purpose is buried in dense prose and the opening phrase 'Unified, chartless context' is a bit abstract; it 's not as crisp as a direct 'Retrieves financial-market context'.

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 provides explicit when-to-use and when-not-to-use guidance: 'Use Undertow instead when the question is specifically about executable depth, liquidity-provider concentration, or position-sized exit cost.' It also explains when to use the 'all' section (when verified China context and NBS source linkage must appear together). This is clear and actionable for an agent.

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

All Seiche — world-markets evidence terminal 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

A4.1/5.0
Disambiguation4/5

The tools are largely separated by domain — funding, fx, oil, crypto, flows, historical day, and health — and the long descriptions make the relationships clear. Still, the broad context tools overlap in cover for mixed cross-market, and there are a few tool pairs with shared concepts (e.g. `funding_stress_now` vs `money_market_context`, or `money_market_context` vs `world_market_context`) that require an agent to read carefully to pick the right one.

Naming Consistency4/5

All tools consistently use lower_snake_case and long informational noun-phrase names, so there is a clear internal style rather than personalized as a fixed verb_noun pattern. The names read predictably as domain-specific evidence tools; only the noun/verse asymmetry from trivial subjects and adjectives is enough to leave a small amount of irregularity.

Tool Count5/5

Eleven tools is a reasonable size for a specialized evidence terminal: each tool adds a distinct evidence or context capability — live funding, health, history, backtest, flows, assets, and broad context. No tool feels redundant or pure padding.

Completeness5/5

The set covers the full reading workflow: current state, granular context, historical analog, proof and health checks, plus specific stress-excessive modules for oil, FX/commodities, and crypto. The terminal scope is evidence/context only and the tools clearly declare their restrictions, so there are no egregious dead-ends within its stated purpose.

Resources