STEM — Persistent AI Memory

List private STEM files

list_files

Read-onlyIdempotent

List this account’s private files and attachment metadata. Does not make a public sharing link.

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": "list_files"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No

Output Schema

Name	Required	Description	Default
`assets`	No
`partBytes`	No
`nextCursor`	No
`capabilities`	No
`maxFileBytes`	No
`currentCatalog`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- addedOutput schema / properties / assets / items / properties / downloadUrl
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
- addedOutput schema / properties / assets / items / properties / viewUrl
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
AddedOct 26, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, closed-world, so the safety profile is fully covered. The description adds that it returns attachment metadata and confirms no sharing link is created, which is mildly useful but largely overlaps the read-only annotation.

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?

Two short sentences, front-loaded with the core action and no filler. The side-effect clause is compact and worth keeping.

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 values need not be explained, and annotations carry the safety profile. Only pagination behavior is left unaddressed, which is a minor but real gap for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter (cursor) has 0% schema description coverage and the description never mentions pagination or cursors. For a paginated listing tool, the description should compensate but does not, leaving the agent to guess at cursor semantics.

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?

States a specific verb (List) and resource (private files and attachment metadata), scoped to 'this account'. The 'private' qualifier separates it from public-sharing siblings like link, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the verb 'List'. The second sentence 'Does not make a public sharing link' implicitly points to the link sibling for sharing, but there is no explicit when-to-use or when-not-to-use guidance.

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

All STEM — Persistent AI Memory 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?