Skip to main content
Glama
Sign In

AgentMart core tools

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

List my memory locker

locker_list
Read-only

List keys in your memory locker (sorted, up to limit per call). While next_after is not null, call again with after = next_after for the next page.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 50,
      "prefix": "notes/",
      "instance_id": "lkr_exampleexampleexample2"
    },
    "name": "locker_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonext_after of your previous call: only keys after it.
limitNoKeys per call, 1 to 1000 (default 200).
prefixNoOnly keys starting with this, e.g. "notes/".
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior the annotations don't: results are sorted and the tool paginates via a next_after cursor. It still doesn't say what the response looks like beyond implying a next_after field.

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?

One sentence plus a parenthetical, front-loaded with the action, and the pagination rule follows immediately. No filler.

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?

There is no output schema, yet the description conveys the one return field that matters for continued calling (next_after) and the ordering guarantee. The remaining gap—full response shape—is minor for a list tool whose annotations already establish it as a safe read.

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 each parameter is already documented, including 'after' and 'limit'. The description adds only the loop-level framing that ties after to next_after; prefix and instance_id get nothing extra. Baseline 3 applies.

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 and resource ('List keys in your memory locker') and scopes it as sorted with a per-call limit. It is distinguishable from locker_get/locker_put/locker_delete by being the enumeration operation, though it never names those siblings 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?

Gives a concrete pagination procedure ('while next_after is not null, call again with after = next_after'), which is real usage guidance for repeated calls. However it offers no guidance on when to use this versus locker_get, nor does it mention the available prefix filtering as a narrowing strategy.

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

All AgentMart core tools 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