Skip to main content
Glama
Sign In
waiaas

waiaas

by waiaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_credentials

List credential metadata for a wallet, including names, types, and expiry dates, without exposing sensitive values.

Instructions

List credential metadata for a wallet (names, types, expiry -- never shows values).

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

Input Schema

NameRequiredDescriptionDefault
wallet_idNoWallet ID. Auto-resolved for single-wallet sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.11.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description bears full responsibility. It transparently discloses the critical limitation 'never shows values' and clarifies it returns metadata only. However, it does not mention other behaviors like response format or potential rate limits, though for a simple list operation this is adequate.

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?

The description is a single sentence of 13 words, directly stating the verb and resource, with key details front-loaded. No unnecessary words or repetition.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the essential purpose, parameter behavior, and a critical behavioral trait. It could optionally describe the return format (e.g., list of objects), but the listed fields (names, types, expiry) give sufficient context.

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?

The input schema has 100% coverage with a description for wallet_id. The description adds minimal semantic value beyond the schema, only reinforcing that the tool works per wallet and noting auto-resolution for single-wallet sessions.

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?

Clearly states the tool lists credential metadata for a wallet, specifies the included fields (names, types, expiry), and explicitly notes it never shows values, distinguishing it from credential value retrieval tools and other list tools among siblings.

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?

Provides implicit guidance by stating 'never shows values' and auto-resolution for single-wallet sessions, but lacks explicit when-to-use or alternatives. The description hints, but does not fully direct the agent when to choose this tool over others.

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

Deploy Server

Other Tools