Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Mark Inbox Item Read

mark_inbox_read
Idempotent

Set read_at on a single inbox item by its id (from list_signal_inbox or the signals feed resource) — not a signal id. Idempotent — re-marking does NOT reset the first-read timestamp; there is no unmark. Returns the new unread_count so the agent/UI can update its badge without a follow-up call. A call that actually marked an unread item returns undo (call undo_change to make it unread again; refused if the item was dismissed or changed since); an already-read item returns undo: null. Tier: sp500+ (sample rejected).

Input Schema

NameRequiredDescriptionDefault
inbox_idYesIdentifier of the inbox item to mark read, as returned by list_signal_inbox or the signals feed resource.

Output Schema

NameRequiredDescriptionDefault
undoYesHow to put the record back as it was before this write: call `undo_change` with these args. Null when nothing changed or the change could not be recorded.
_metaYesProvenance envelope — data lineage for every MCP response
inbox_idYes
marked_readYes
unread_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / undo
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "args": {
+          "additionalProperties": false,
+          "properties": {
+            "change_id": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "change_id"
+          ],
+          "type": "object"
+        },
+        "tool": {
+          "const": "undo_change",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool",
+        "args"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How to put the record back as it was before this write: call `undo_change` with these args. Null when nothing changed or the change could not be recorded."
+}
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "inbox_id",
-  "marked_read",
-  "unread_count"
-]New value: +[
+  "_meta",
+  "inbox_id",
+  "marked_read",
+  "unread_count",
+  "undo"
+]
  2. Changed1 schema field changed
    • 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."
  3. Changed2 schema fields changed
    • 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)."
  4. Added
  5. Removed
  6. Changed1 schema field changed
    • 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."
  7. Changed1 schema field changed
    • changedInput schema / properties / inbox_id / description
      Previous value: -"Identifier of the inbox item to mark read, as returned by list_alert_inbox or the alerts feed resource."New value: +"Identifier of the inbox item to mark read, as returned by list_signal_inbox or the signals feed resource."
  8. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / fundamentals_as_of
      Added value: +{
+  "description": "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.",
+  "type": "string"
+}
    • addedOutput schema / properties / _meta / properties / price_as_of
      Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}
  9. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / cost_usd
      Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / _meta / properties / latency_ms
      Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}
  10. Changed1 schema field changed
    • addedOutput schema / properties / _meta / properties / pit_safe / description
      Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
  11. Changed1 schema field changed
    • addedInput schema / properties / inbox_id / description
      Added value: +"Identifier of the inbox item to mark read, as returned by list_alert_inbox or the alerts feed resource."
  12. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that re-marking does not reset the first-read timestamp, that there is no unmark operation, that the response includes the new unread_count (avoiding a follow-up call), and the exact undo-token contract including when undo is refused. This is unusually rich behavioral detail for a low-risk mutation.

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?

Front-loaded with the core action, then idempotency, then return/undo semantics, then the tier gate — a sensible priority order. It is dense with parentheticals and em-dashes, so it reads slightly packed, but no sentence is 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?

An output schema exists, yet the description still flags the two response fields an agent must branch on (unread_count and undo/null), covering the decision logic the schema alone would not convey. Combined with annotations and 100% param coverage, nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real value by clarifying that the id must come from the inbox listing and is NOT a signal id — a namespace confusion the schema text alone does not resolve. Length/format constraints remain schema-only.

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 ('Set `read_at` on a single inbox item by its id') and explicitly distinguishes the identifier namespace from a signal id. An agent can tell this apart from dismiss_inbox_item or any signal-mutating sibling without opening the schema.

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?

Names the source of the id (list_signal_inbox or the signals feed resource) and routes the agent to `undo_change` for reversal, plus states the tier gate (sp500+). It does not explicitly contrast with the closest sibling, dismiss_inbox_item, so the boundary between marking read vs dismissing is left implicit.

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 toolsInspect
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