Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Test Signal (synthetic fire)

test_signal

Fire a synthetic notification through EVERY channel the signal is configured with. Use this immediately after create_signal to verify the channels (email address valid / webhook URL reachable + HMAC verification on the receiver). The synthetic fire is logged with a [TEST] summary so it affects neither the real fire counter nor the one-email-per-day cap — the next genuine match still fires normally. channel_type/outcome describe the FIRST channel; channel_results lists every channel's own outcome.

Input Schema

Name	Required	Description	Default
`signal_id`	Yes	Identifier of the signal to fire a synthetic test notification through, as returned by create_signal or list_signals.

Output Schema

Name	Required	Description
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`outcome`	Yes
`signal_id`	Yes
`status_code`	Yes
`channel_type`	Yes
`error_message`	Yes
`channel_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."

changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description

Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."

AddedOct 16, 2026
RemovedSep 29, 2026

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / _meta / properties / fundamentals_as_of / description

Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties / channel_results

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "channel_type": {
+        "enum": [
+          "email",
+          "webhook",
+          "slack",
+          "dashboard",
+          "agent_run"
+        ],
+        "type": "string"
+      },
+      "error_message": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "outcome": {
+        "enum": [
+          "success",
+          "retry",
+          "dead",
+          "skipped"
+        ],
+        "type": "string"
+      },
+      "status_code": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "outcome",
+      "channel_type",
+      "status_code",
+      "error_message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "signal_id",
-  "outcome",
-  "channel_type",
-  "status_code",
-  "error_message"
-]New value: +[
+  "_meta",
+  "signal_id",
+  "outcome",
+  "channel_type",
+  "status_code",
+  "error_message",
+  "channel_results"
+]

AddedAug 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the fire is logged with a `[TEST]` summary, does not increment the real fire counter, and does not consume the one-email-per-day cap, so the next genuine match still fires. This is exactly the side-effect information an agent needs for a non-readOnly, openWorld call with idempotentHint=false. It stops short of noting rate limits or delivery failure handling, so not a 5.

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?

Four sentences, front-loaded with the action and the trigger, and each sentence carries new information (channels, verification targets, counter/cap behavior, output shape). Slightly dense with backticked field names, but no filler.

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?

Covers what the tool does, when to call it, the side-effect profile that an agent cannot infer from annotations, and clarifies the output fields (channel_type/outcome vs channel_results) despite an output schema existing. Nothing material is missing for correct invocation.

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?

There is a single parameter, signal_id, already fully documented in the schema (100% coverage), including its provenance from create_signal/list_signals. The description does not add format or constraint detail beyond that, so the baseline 3 applies; the output-field explanation belongs to return shape rather than parameter meaning.

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?

States a specific verb and resource (fire a synthetic notification) and immediately scopes it ('EVERY channel the signal is configured with'), which cleanly separates it from create_signal, update_signal, and test_rule. The synthetic/test nature of the fire is unambiguous.

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?

Gives an explicit trigger ('Use this immediately after create_signal to verify the channels') plus the concrete verifications it performs (email validity, webhook reachability, HMAC). An agent knows exactly when to reach for this tool rather than list_signals or update_signal.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.