Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Get Agent Memory

get_agent_memory

Read-onlyIdempotent

Recall this user's durable memory. Omit key (or pass null) to read EVERYTHING you have remembered, newest-first — do this at the START of a task to re-ground yourself. Pass a specific key to fetch one entry. An absent key returns an empty list, never an error (absence is a first-class answer). Tier: sp500+ (sample rejected).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_memory"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No	A specific key to fetch, or omit/null to recall all memory (newest-first).

Output Schema

Name	Required	Description	Default
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: results are newest-first, an absent key returns an empty list rather than an error, and access requires the sp500+ tier.

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?

Front-loads the core purpose, then the null/omission rule and the task-start recommendation, ending with a compact entitlement note. No sentence is redundant despite the density.

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 detail is unnecessary, and the description covers modes, ordering, empty-result behavior and entitlements. The only minor gap is not contrasting with the mutation siblings, which is low-risk for a read-only recall tool.

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% and the schema already explains the key/null semantics, so the baseline would be 3. The description adds the outcome of the absent-key case (empty list, not an error) and the ordering, which the schema does not convey.

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 ('Recall this user's durable memory') and immediately clarifies the two modes: all memory vs. one key. It is clearly separable from set_agent_memory and delete_agent_memory in the sibling list.

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?

Gives explicit situational guidance ('do this at the START of a task to re-ground yourself') plus a conditional rule for when to pass a key. It does not name the write-side siblings (set_agent_memory, delete_agent_memory) as alternatives, so a 4 rather than a 5.

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.