Skip to main content
Glama
Sign In

agent-memory

by dev.veritap
OverviewDiscussionsAdmin

Your storage account status (free)

locker_status

Free. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "locker_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesEVM wallet address (0x…, the mailbox identity).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully adds that the tool is free and discloses the set of returned account metrics, which is relevant behavioral context. However, it does not explicitly state read-only behavior, permissions, or other operational traits beyond the word 'status' and the listed values.

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?

The description is very compact and has no wasted words: 'Free' is front-loaded, and the metric list is short. It is slightly telegraphic and could be improved with a verb, but it remains efficient and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool, the description is adequate: a caller knows the required address and the high-level fields returned. But there is no output schema, and the description does not explain units, value formats, or possible grace-state values, so an agent is left guessing at the exact response shape.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the single `address` parameter, including its EVM format and mailbox-identity meaning. The description only repeats 'for an address' without adding new parameter-level semantics, which matches the baseline for fully covered schema parameters.

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?

The title and description clearly identify this as a storage-account status tool and enumerate the specific metrics returned: credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state. However, the description lacks an explicit verb like 'retrieves' or 'returns,' and it does not directly distinguish itself from overlapping siblings such as locker_credit or locker_checkpoint.

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?

The description implies usage when a caller wants an aggregate storage-account status view, and the field list clarifies what that view contains. But it provides no explicit guidance on when to prefer this tool over siblings, nor does it state any exclusions or alternatives.

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

All agent-memory 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