Skip to main content
Glama

fahali_subscribe_risk

Idempotent

Deliver monitor-only observations and risk alerts idempotently via signed webhook, agent callback, Slack, Teams, email, or push; excludes recommendations, portfolio actions, orders, and execution.

Instructions

Idempotently deliver monitor-only observations and risk alerts through a signed webhook, agent callback, Slack, Teams, account email, or registered push device. Delivery policy structurally prohibits personalized recommendations, portfolio actions, orders, and execution. A generated signing secret is recoverable only through the exact authenticated idempotent request; a changed request requires a new key.

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum rows per projectable collection. Audit has no MCP projection cap; brief defaults to 3 and standard to 12.
sinceNoOptional lower timestamp bound for returned row collections.
detailNoResponse depth. audit is the full-fidelity default; brief and standard are explicit compact projections.audit
eventsNo
channelYes
symbolsNoOptional symbol projection, as a comma-separated string or array. Rows without instrument identity are not discarded.
watch_idYes
target_urlNoRequired for webhook, agent_callback, Slack, and Teams. Public HTTPS only.
minimum_actionNoLegacy monitoring-escalation threshold only; never a portfolio or order action.WATCH
signing_secretNoOptional for webhook/callback. Omit to generate one returned on creation and recoverable by an exact authenticated idempotent replay while that subscription configuration remains current.
idempotency_keyYesRequired retry identity for this write. Reuse only for an identical owner, operation, and request; a changed request with the same key fails closed.
include_withheldNoInclude full withheld-row detail. Defaults true with audit; explicitly set false only for a compact projection.

Output Schema

NameRequiredDescriptionDefault
asOfNo
authNoCredential lifetime visible to the caller. OAuth secondsRemaining lets an autonomous agent refresh before a multi-call workflow is interrupted.
claimNoFahali 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.
deltaNo
itemsNo
scopeNo
watchNo
statusYes
absenceNoWhy no actionable finding is present: measured_empty, user_empty, no_coverage, source_unverified, stale, withheld, source_error, auth_failure, or entitlement_required.
verdictNo
watchesNo
decisionNo
conflictsNo
dataStateYes
mcpStatusNoNormalized MCP result status. The endpoint's original status vocabulary remains in `status` and `sourceStatus`.
refreshedNo
requestIdNo
verdictIdNo
nextCursorNo
validUntilNo
claimPolicyNoTyped constraints for safe use. Metadata, not a prompt or instruction channel.
idempotencyNo
instrumentsNoResolved or explicitly partial instrument identities. A missing venue carries an ambiguity warning.
nextActionsNoRegistry-validated follow-up calls. Missing tools, invalid arguments, unresolved placeholders, and disabled tools are omitted.
sourceErrorNoThe upstream endpoint's exact error text/code before normalization, when one was present.
sourceScopeNo
decisionHashNo
evidenceHashNo
sourceStatusNoThe upstream endpoint's exact status before the MCP envelope normalizes transport success/error.
subscriptionNo
agentBriefingNoAudit-only narrative projection. Present only when detail='audit'; compact responses do not duplicate structured data as prose.
claimValidityNoValidity of the selected binding claim only, calculated after filtering, projection and row selection. Sibling rows cannot determine it.
operatingModeYes
responseStateNo
schemaVersionNo
signingSecretNo
subscriptionsNo
authorityStateNo
sourceDecisionNo
symbolCoverageNoConservation ledger satisfying requested = returned + withheld + notReturned for requested-symbol calls.
evidenceQualityNo
responseControlNo
sourceDataStateNoThe upstream endpoint's exact data-state value before endpoint-aware classification.
evidenceSnapshotNoCompact immutable source snapshot needed to verify evidenceRef integrity on delta responses.
recordMatchReasonNoWhy matchedTrackRecord is present or null. A null record is never evidence of safety or engine failure.
signingSecretNoteNo
matchedTrackRecordNoA 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.
methodologyVersionNo
confidenceSemanticsNoEvery confidence-bearing value with its score type, scale, calibration status, and probability flag.
decisionEligibilityNoFail-closed binding-authority policy. WITHHELD means source evidence remains available for audit while normalized direction, actionability and execution fields are revoked.
directionEligibilityNoCurrent 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.
executionEligibilityNoFail-closed execution boundary. Portfolio monitoring tools always return WITHHELD with MONITOR_ONLY_NO_EXECUTION_AUTHORITY while Fahali has no capital path.
legacyFieldSemanticsYes
outputClassificationYes
monitoringEligibilityNoCurrent portfolio-monitoring validity based on captured identity, freshness, integrity, and the caller-supplied monitoring policy. ELIGIBLE authorizes observation/delivery only, never financial action.
sourceEvidenceQualityNo
currentActionEligibilityNoCurrent eligibility of an immutable historical portfolio verdict. It never mutates the stored judgment being replayed.
sourceConfidenceSemanticsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.28.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the description's job is to add beyond that. It does: a structural policy guarantee that no recommendations, portfolio actions, orders, or execution flow through this channel, plus the rule that a generated signing secret survives only an exact authenticated replay and is lost on any changed request. Remaining gaps are rate limits and delivery retry behavior.

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 front-loaded sentences: what it delivers, what it will never deliver, and the secret/idempotency consequence. Dense but no filler; the middle policy sentence is arguably defensive boilerplate rather than operational guidance.

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?

An output schema exists, so return shape need not be explained, and the schema carries the channel-conditional target_url requirement. With 12 parameters and 3 enums, the description covers the operation and its key invariant (idempotency key identity) adequately; only the required watch_id/channel pairing and the events filter are left entirely to the schema.

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 75%, which already documents target_url HTTPS rules, idempotency-key reuse semantics, detail levels, and signing_secret generation. The description restates the signing-secret recovery rule and the fail-closed idempotency behavior, but adds no new syntax or constraint beyond the schema, so baseline 3 applies.

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?

States the operation (idempotent delivery of monitor-only observations and risk alerts) and enumerates every supported channel, so the agent knows exactly what gets created. It does not distinguish itself from closely related siblings such as fahali_create_alert, fahali_update_subscription, or fahali_get_realtime_alerts, which is the only thing keeping it from a 5.

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 by the channel list and the policy statement (this is the setup path for pushed risk notifications), and the secret-recovery sentence hints at the replay use case. However, there is no explicit when-to-use versus fahali_create_alert or fahali_update_subscription, and no stated when-not-to-use conditions.

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

Deploy Server

Other Tools