n0brains

Get Signal

get_signal

Read-only

[RAW FEED — detail] Fetch a single signal by ID with full enrichment (historical_edge, paired_inverse, latency, priced_in fields). Returns 404 semantics via tool error if signal not found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`asset`	No
`score`	No
`source`	No
`channel`	No
`content`	No
`sources`	No
`summary`	Yes
`urgency`	No
`direction`	Yes
`timestamp`	Yes
`confidence`	No
`conviction`	No
`disclaimer`	No
`expires_at`	No
`action_hint`	No
`asset_class`	No
`signal_type`	Yes
`corroborated`	No
`levels_basis`	No
`target_level`	No
`paired_inverse`	No
`historical_edge`	No
`model_transform`	No
`observed_entity`	No
`priced_in_score`	No
`priced_in_vol_z`	No
`reference_price`	No
`transform_basis`	No
`regime_at_signal`	No
`type_performance`	No
`confidence_status`	No
`expected_move_pct`	No
`observed_behavior`	No
`invalidation_level`	No
`manipulation_score`	No
`observed_direction`	No
`trade_quality_band`	No
`transform_sample_n`	No
`predicted_direction`	No
`signal_latency_secs`	No
`trade_quality_score`	No
`priced_in_ret_1h_pct`	No
`coordinated_pump_prob`	No
`transform_validation_status`	No
`calibration_inverted_in_cell`	No
`confidence_suppressed_reason`	No
`confidence_revised_by_corroboration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedJul 30, 2026

addedOutput schema / properties / confidence_revised_by_corroboration

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confidence Revised By Corroboration"
+}

addedOutput schema / properties / confidence_status

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confidence Status"
+}

addedOutput schema / properties / confidence_suppressed_reason

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confidence Suppressed Reason"
+}

addedOutput schema / properties / model_transform

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Model Transform"
+}

addedOutput schema / properties / observed_behavior

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Observed Behavior"
+}

addedOutput schema / properties / observed_direction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Observed Direction"
+}

addedOutput schema / properties / observed_entity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Observed Entity"
+}

addedOutput schema / properties / predicted_direction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Predicted Direction"
+}

addedOutput schema / properties / transform_basis

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Transform Basis"
+}

addedOutput schema / properties / transform_sample_n

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Transform Sample N"
+}

addedOutput schema / properties / transform_validation_status

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Transform Validation Status"
+}

Changed1 schema field changedJul 24, 2026

removedOutput schema / properties / signal_type / enum

Removed value: -[
-  "regulatory",
-  "whale",
-  "whale_position",
-  "sentiment",
-  "price",
-  "hack",
-  "listing",
-  "unlock",
-  "macro",
-  "macro_flow",
-  "macro_pulse",
-  "liquidation",
-  "funding",
-  "research",
-  "deleverage",
-  "options_flow",
-  "dex_flow",
-  "other"
-]

Changed1 schema field changedJul 21, 2026

changedOutput schema / properties / signal_type / enum

Previous value: -[
-  "regulatory",
-  "whale",
-  "whale_position",
-  "sentiment",
-  "price",
-  "hack",
-  "listing",
-  "unlock",
-  "macro",
-  "macro_flow",
-  "macro_pulse",
-  "liquidation",
-  "funding",
-  "research",
-  "deleverage",
-  "options_flow",
-  "other"
-]New value: +[
+  "regulatory",
+  "whale",
+  "whale_position",
+  "sentiment",
+  "price",
+  "hack",
+  "listing",
+  "unlock",
+  "macro",
+  "macro_flow",
+  "macro_pulse",
+  "liquidation",
+  "funding",
+  "research",
+  "deleverage",
+  "options_flow",
+  "dex_flow",
+  "other"
+]

Changed1 schema field changedJul 20, 2026

changedOutput schema / properties / signal_type / enum

Previous value: -[
-  "regulatory",
-  "whale",
-  "whale_position",
-  "sentiment",
-  "price",
-  "hack",
-  "listing",
-  "unlock",
-  "macro",
-  "macro_flow",
-  "macro_pulse",
-  "liquidation",
-  "funding",
-  "research",
-  "deleverage",
-  "other"
-]New value: +[
+  "regulatory",
+  "whale",
+  "whale_position",
+  "sentiment",
+  "price",
+  "hack",
+  "listing",
+  "unlock",
+  "macro",
+  "macro_flow",
+  "macro_pulse",
+  "liquidation",
+  "funding",
+  "research",
+  "deleverage",
+  "options_flow",
+  "other"
+]

First observedJul 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds behavioral detail beyond the readOnlyHint annotation by disclosing that a not-found signal returns 404 semantics via tool error. Also clarifies the enrichment fields included, which is useful but not extensive.

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

Conciseness5/5

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

Two sentences with a front-loaded label '[RAW FEED — detail]' and no unnecessary verbiage. Every word adds value.

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 retrieval tool, the description covers input (by ID), behavior (404 error), and output enrichment fields. Output schema exists, so return format details are not required in the description.

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?

The only parameter 'id' is referenced as 'by ID', making its purpose clear. However, schema coverage is 0% and the description doesn't provide format, range, or example, though for an integer ID this is minimally sufficient.

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?

Clearly states it fetches a single signal by ID, with an explicit list of enrichment fields (historical_edge, paired_inverse, latency, priced_in). Distinguishes from siblings like list_signals (list vs single) and get_signal_with_context (raw vs contextual).

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

Usage Guidelines4/5

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

Implies usage for retrieving a specific signal with full raw detail when you have the ID. Does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it over list_signals or get_signals_since.

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

All n0brains 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.

Resources

Need Help?