Skip to main content
Glama

amem_skill_list

List stored agent skills as a name-and-description index, optionally ranked by task, so you can pick which procedure to load next.

Instructions

List stored skills (procedures the agent learned) as an index of names and descriptions only. Cheap — call this first, then amem_skill_view to load the one you need. Skills are longer procedures; use amem_context for small durable facts. All arguments are optional.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional: rank the index against this task description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.5
    • addedInput schema / required
      Added value: +[]
  2. First observedv0.4.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral traits: the response is an index only (no procedure bodies), and the call is cheap by design. It stops short of stating read-only semantics outright or whether results are paginated/truncated, so it is strong but not exhaustive for a zero-annotation tool.

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?

Four short clauses, front-loaded with what the tool returns and why it is cheap, then the routing guidance. No sentence is filler; even the definitional aside about skills prevents a wrong-sibling call.

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 single-optional-param list tool with no output schema and no annotations, the description covers purpose, return shape, cost, call ordering, and the nearest competing tool. Nothing an agent needs in order to invoke it correctly is missing.

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 coverage is 100% and the single 'query' parameter is already documented as ranking the index against a task description, so the schema does the heavy lifting. The description only adds 'All arguments are optional', which restates the empty required list rather than adding new meaning.

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 ('List stored skills') plus the exact return shape ('an index of names and descriptions only'), and parenthetically defines what a skill is. It also distinguishes itself from amem_skill_view and amem_context by naming both siblings, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit call order ('call this first, then amem_skill_view to load the one you need') and an explicit exclusion rule ('Skills are longer procedures; use amem_context for small durable facts'). This is the when/when-not/alternative triad in three sentences.

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