Skip to main content
Glama

list_accounts

Read-only

List your accounts

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: no mention of result volume, pagination, ordering, or whether all accounts or only the caller's are returned. Given a four-word sentence, essentially zero behavioral context is contributed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with no filler, so it is trivially concise and front-loaded. However, the brevity is under-specification rather than efficiency — the single sentence carries almost no information the name does not already convey.

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

Completeness2/5

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

For a zero-parameter read tool there is no output schema, so the description is the only place to learn what comes back (account identifiers, names, counts) and whether the list is scoped to the authenticated user. It supplies none of that, leaving the agent unable to predict the response shape.

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?

The input schema has zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description does not confuse things with phantom parameter talk, and "your" at least implies an implicit caller scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List your accounts" names a verb and resource, so the basic operation is understandable. But it never clarifies what an "account" is here (player account, organization, API tenant) or how it differs from siblings like get_account_overview, get_current_user, or get_player_report. The purpose is only minimally specific.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. With 48 siblings including get_account_overview and get_current_user, the agent is given no hint whether list_accounts is for enumerating all accounts versus fetching a single one, nor any prerequisite or exclusion information.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources