Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Submit Feedback

submit_feedback

File product feedback to the Valuein team — a bug, feature request, experience note, or data-quality issue — directly from the agent surface. Available on EVERY tier including guest/sample (no token required), so an agent can report a rough edge in-band without the human leaving the conversation. Provide a category and a message (other fields optional — see params). Authenticated callers can pass an idempotency_key so a retried submission files exactly once (the same key from the same account); guest/sample callers are never deduplicated. Returns a friendly acknowledgment you can relay to the user. Do NOT use this to query data; it is a one-way report channel. Never quote or paste the person's research (report text, notes, uploaded documents, watchlists, agent memory, or figures from their reports): it is private and theirs. Describe the problem in your own words and point at it by id (target_id, request_id, fact_id with its ticker).

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional structured error-mode reason: 'wrong_number', 'bad_citation', 'missing_data', 'wrong_company', 'formatting', 'hallucinated_fact', 'tool_error', 'coverage_gap', or 'other'.
contextNoOptional free-form context object (stored as JSON), e.g. { tool: 'get_company_fundamentals', ticker: 'AAPL', request_id: 'abc123' }. Avoid secrets.
fact_idNoOptional disputed `fact_id` (for wrong_number / bad_citation feedback).
messageYesThe feedback body (1–4000 chars). Be specific: what you expected, what happened, and any reproduction steps. Stored for triage and never used for arithmetic. The person's own words about the product, or yours; never a copy of their research. Do not paste research into it.
subjectNoOptional short title (≤140 chars) summarizing the feedback.
surfaceNoOptional product surface the feedback concerns: 'mcp', 'workspace', 'sdk', 'dashboard', or 'api'.
categoryYesWhat kind of feedback this is: 'bug' (something broke), 'feature_request' (something missing), 'experience' (UX / clarity / docs), 'data_quality' (a wrong/missing/stale figure), or 'other'.
severityNoOptional impact classification: 'low', 'medium', or 'high'.
sentimentNoOptional sentiment of this feedback: 'positive' (worked well), 'negative' (something was wrong), or 'correction' (you are supplying the right value).
target_idNoOptional id of the artifact this feedback targets (e.g. a report id).
request_idNoOptional `_meta` request id of the turn that produced the artifact, for correlation.
target_typeNoOptional kind of artifact the feedback targets: 'chat_message', 'report', 'tool_call', 'schema', or 'other'.
expected_valueNoOptional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data. The person's own words about the product, or yours; never a copy of their research.
idempotency_keyNoOptional client-supplied key (1–64 chars). For authenticated callers, reusing the same key files the feedback exactly once — safe to retry on a network error. Ignored for guest/sample callers (no account to scope dedup to).

Output Schema

NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
feedbackYes
acknowledgmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / expected_value / description
      Previous value: -"Optional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data."New value: +"Optional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data. The person's own words about the product, or yours; never a copy of their research."
    • changedInput schema / properties / message / description
      Previous value: -"The feedback body (1–4000 chars). Be specific: what you expected, what happened, and any reproduction steps. May contain the user's own words — it is stored for triage and never used for arithmetic."New value: +"The feedback body (1–4000 chars). Be specific: what you expected, what happened, and any reproduction steps. Stored for triage and never used for arithmetic. The person's own words about the product, or yours; never a copy of their research. Do not paste research into it."
    • changedInput schema / properties / target_id / description
      Previous value: -"Optional id of the artifact this feedback targets (e.g. a report or thesis id)."New value: +"Optional id of the artifact this feedback targets (e.g. a report id)."
    • changedInput schema / properties / target_type / description
      Previous value: -"Optional kind of artifact the feedback targets: 'chat_message', 'report', 'thesis', 'claim', 'tool_call', 'schema', or 'other'."New value: +"Optional kind of artifact the feedback targets: 'chat_message', 'report', 'tool_call', 'schema', or 'other'."
    • changedInput schema / properties / target_type / enum
      Previous value: -[
-  "chat_message",
-  "report",
-  "thesis",
-  "claim",
-  "tool_call",
-  "schema",
-  "other"
-]New value: +[
+  "chat_message",
+  "report",
+  "tool_call",
+  "schema",
+  "other"
+]
  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. 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"
+}
  8. 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"
+}
  9. Changed7 schema fields changed
    • addedInput schema / properties / expected_value
      Added value: +{
+  "description": "Optional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data.",
+  "maxLength": 4000,
+  "type": "string"
+}
    • addedInput schema / properties / fact_id
      Added value: +{
+  "description": "Optional disputed `fact_id` (for wrong_number / bad_citation feedback).",
+  "maxLength": 256,
+  "type": "string"
+}
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Optional structured error-mode reason: 'wrong_number', 'bad_citation', 'missing_data', 'wrong_company', 'formatting', 'hallucinated_fact', 'tool_error', 'coverage_gap', or 'other'.",
+  "enum": [
+    "wrong_number",
+    "bad_citation",
+    "missing_data",
+    "wrong_company",
+    "formatting",
+    "hallucinated_fact",
+    "tool_error",
+    "coverage_gap",
+    "other"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Optional `_meta` request id of the turn that produced the artifact, for correlation.",
+  "maxLength": 256,
+  "type": "string"
+}
    • addedInput schema / properties / sentiment
      Added value: +{
+  "description": "Optional sentiment of this feedback: 'positive' (worked well), 'negative' (something was wrong), or 'correction' (you are supplying the right value).",
+  "enum": [
+    "positive",
+    "negative",
+    "correction"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target_id
      Added value: +{
+  "description": "Optional id of the artifact this feedback targets (e.g. a report or thesis id).",
+  "maxLength": 256,
+  "type": "string"
+}
    • addedInput schema / properties / target_type
      Added value: +{
+  "description": "Optional kind of artifact the feedback targets: 'chat_message', 'report', 'thesis', 'claim', 'tool_call', 'schema', or 'other'.",
+  "enum": [
+    "chat_message",
+    "report",
+    "thesis",
+    "claim",
+    "tool_call",
+    "schema",
+    "other"
+  ],
+  "type": "string"
+}
  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. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: tier availability including unauthenticated guests, the fact that guest submissions are never deduplicated, that authenticated retries with the same idempotency_key file exactly once, that it returns a relayable acknowledgment, and that expected_value is stored verbatim but never trusted as data. The optional idempotency key is consistent with idempotentHint=false (idempotency is opt-in, not the default), so no contradiction.

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 purpose and availability before the privacy constraint, and nearly every sentence carries operational weight. It is a dense single block, though, and the "never a copy of their research" instruction is stated in the description as well as repeated in the message and expected_value schema fields.

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 14-parameter tool with a nested context object, six enums, full schema coverage, and an output schema, the description covers everything an agent needs: when to use it, auth-free access, dedup semantics, privacy limits on what may be pasted, and that the return value is a relayable acknowledgment.

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 meaning: it names the two required fields (category, message), explains the idempotency_key's account-scoped dedup behavior, and gives concrete id-pointing guidance for target_id, request_id, and fact_id. It still delegates most per-field detail to the schema with "see params", which is appropriate.

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?

"File product feedback to the Valuein team" is a specific verb plus resource, and the enumerated categories (bug, feature request, experience note, data-quality issue) pin down the scope precisely. It stops short of distinguishing itself from the near-identical sibling submit_artifact_feedback, which is the one confusion an agent could reasonably hit.

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?

Strong when/when-not coverage: "Available on EVERY tier including guest/sample (no token required)", "Do NOT use this to query data; it is a one-way report channel", plus an explicit rule about not pasting the user's research and instead pointing by id. The only missing piece is routing versus submit_artifact_feedback, so an agent has no stated alternative for that decision.

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