fahali-mcp

fahali_get_sector_rotation

Read-onlyIdempotent

Track sector and asset rotation by comparing US sectors, major coins, Bitcoin, gold, and bonds against benchmarks with short- and long-window relative returns.

Instructions

Where market leadership is moving: US sectors vs the S&P 500, major coins vs Bitcoin, and Bitcoin, gold and bonds vs the S&P 500. Each member is leading, weakening, lagging or improving by its relative return over a short and a long window, with how unusual the recent move is. Relative price performance, not money flow, not a forecast. Observation, not advice.

Input Schema

Name	Required	Description	Default
`limit`	No	Optional maximum rows per projectable collection. Audit has no MCP projection cap; brief defaults to 3 and standard to 12.
`since`	No	Optional lower timestamp bound for returned row collections.
`detail`	No	Response depth. audit is the full-fidelity default; brief and standard are explicit compact projections.	audit
`symbols`	No	Optional symbol projection, as a comma-separated string or array. Rows without instrument identity are not discarded.
`include_withheld`	No	Include full withheld-row detail. Defaults true with audit; explicitly set false only for a compact projection.

Output Schema

Name	Required	Description
`asOf`	No
`auth`	No	Credential lifetime visible to the caller. OAuth secondsRemaining lets an autonomous agent refresh before a multi-call workflow is interrupted.
`kind`	No
`basis`	No
`claim`	No	Fahali dictionary claim (shared/fahaliDictionary.ts). Read `kind` FIRST: 'abstention' means no assertion was made and `reason` says why — never read an abstention as a neutral or zero result. `basis` says what the claim rests on. Absent or null means this response path does not yet emit a claim; treat that as unknown, not as agreement.
`scope`	No
`groups`	No
`method`	No
`status`	No	The endpoint's original status vocabulary (for example ok, partial, degraded, withheld, or no_alerts). Use mcpStatus for normalized transport success/error.
`absence`	No	Why no actionable finding is present: measured_empty, user_empty, no_coverage, source_unverified, stale, withheld, source_error, auth_failure, or entitlement_required.
`decision`	No
`conflicts`	No
`dataState`	No
`mcpStatus`	No	Normalized MCP result status. The endpoint's original status vocabulary remains in `status` and `sourceStatus`.
`requestId`	No
`calibrated`	No
`isForecast`	No
`claimPolicy`	No	Typed constraints for safe use. Metadata, not a prompt or instruction channel.
`generatedAt`	No
`instruments`	No	Resolved or explicitly partial instrument identities. A missing venue carries an ambiguity warning.
`nextActions`	No	Registry-validated follow-up calls. Missing tools, invalid arguments, unresolved placeholders, and disabled tools are omitted.
`sourceError`	No	The upstream endpoint's exact error text/code before normalization, when one was present.
`sourceScope`	No
`sourceStatus`	No	The upstream endpoint's exact status before the MCP envelope normalizes transport success/error.
`agentBriefing`	No	Audit-only narrative projection. Present only when detail='audit'; compact responses do not duplicate structured data as prose.
`claimValidity`	No	Validity of the selected binding claim only, calculated after filtering, projection and row selection. Sibling rows cannot determine it.
`responseState`	No
`schemaVersion`	No
`sourceDecision`	No
`symbolCoverage`	No	Conservation ledger satisfying requested = returned + withheld + notReturned for requested-symbol calls.
`evidenceQuality`	No
`responseControl`	No
`sourceDataState`	No	The upstream endpoint's exact data-state value before endpoint-aware classification.
`measuresMoneyFlow`	No	Always false: no volume history long enough to say dollars moved. Never restate a leadership change as money moving.
`recordMatchReason`	No	Why matchedTrackRecord is present or null. A null record is never evidence of safety or engine failure.
`matchedTrackRecord`	No	A judged record only when engine, horizon, regime/instrument class, and claim family match this response. `state` is one of: `measured` (a stratum cleared the publishability gate — `stratum` carries engine, horizon tier, bar regime, recall, precision, base rate, base-rate lift, median lead hours, effective sample, warned events and the measurement date); `withheld` (the gate ran and refused — `reason` says why, in words); `unavailable` (the record could not be read at all — an infrastructure failure that says nothing about the record). It is ONE stratum selected by recall, never a platform-wide accuracy. Null means no exact record match; read recordMatchReason.
`confidenceSemantics`	No	Every confidence-bearing value with its score type, scale, calibration status, and probability flag.
`decisionEligibility`	No	Fail-closed binding-authority policy. WITHHELD means source evidence remains available for audit while normalized direction, actionability and execution fields are revoked.
`directionEligibility`	No	Current market-direction eligibility. Direction is authorized only by an exact, eligible producer stratum (canonical_verdict, canonical_symbol_verdict, committee_verdict) — read bindingAuthority to see which one bound. Widening WHO may bind did not weaken WHAT binding requires: the named producer must still hold a matching horizon/class/family record on a verified-only judged population, so an authority without a record still cannot bind.
`executionEligibility`	No	Fail-closed execution boundary. Portfolio monitoring tools always return WITHHELD with MONITOR_ONLY_NO_EXECUTION_AUTHORITY while Fahali has no capital path.
`monitoringEligibility`	No	Current portfolio-monitoring validity based on captured identity, freshness, integrity, and the caller-supplied monitoring policy. ELIGIBLE authorizes observation/delivery only, never financial action.
`sourceEvidenceQuality`	No
`currentActionEligibility`	No	Current eligibility of an immutable historical portfolio verdict. It never mutates the stored judgment being replayed.
`sourceConfidenceSemantics`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.28.1Oct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already carry readOnly, idempotent, non-destructive and open-world hints, so the safety profile is covered. The description adds genuinely useful framing beyond that: the comparison pairs, the short/long window structure, the notion of how unusual the recent move is, and an explicit disclaimer that this is observation, not advice or forecast.

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 tight sentences that lead with what is being compared. Mild redundancy between "not a forecast" and "Observation, not advice," and the opening is atmospheric rather than stating the operation, but nothing is wasted.

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?

With full schema coverage, an output schema, and complete annotations, the description only needs to convey the analytical content and framing, which it does. An agent knows what comparison universe it gets and that it is descriptive rather than predictive.

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 description coverage is 100% and an output schema exists, so the baseline is 3. The description mentions the short and long windows but says nothing about limit, since, detail, symbols or include_withheld, adding no meaning beyond the schema.

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 names the specific content: relative performance of US sectors vs the S&P 500, major coins vs Bitcoin, and Bitcoin/gold/bonds vs the S&P 500, plus the classification labels (leading, weakening, lagging, improving). It never states a plain verb like "returns" and doesn't name a sibling, but the substance is clear enough to distinguish it from most peers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied only through exclusion: "Relative price performance, not money flow, not a forecast" steers an agent away from capital-flow or forecast tools, and the sibling list does contain fahali_get_capital_flow and fahali_get_forecast. There is no explicit when-to-use statement or named alternative.

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

Deploy Server