Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_api_keys

Read-onlyIdempotent

Retrieve your organization's API keys by name and prefix. Use it to review stored key identifiers; full secret keys are never stored and cannot be displayed.

Instructions

List the organization's API keys (slk_…) by name and prefix; full keys are never stored, so they can't be shown.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
apiKeysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that only name and prefix are returned and that full keys are never stored, which stops an agent from expecting or requesting a secret value.

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?

A single front-loaded sentence that delivers the resource, the returned fields, and the key limitation with zero filler. Nothing is redundant with the title or annotations.

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?

With no inputs, a full annotation set, and an output schema that documents the return shape, the description only needs to add the non-obvious constraint about secrets — which it does. An agent has everything required to call it and interpret the result correctly.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly spends no words on inputs.

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?

Names a specific verb and resource ('List the organization's API keys') and even identifies the identifier format ('slk_…'), so an agent knows exactly what entity is being enumerated. It does not explicitly differentiate itself from sibling list_* tools, but the resource is unambiguous enough that confusion is unlikely.

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?

Usage is only implied: the zero-parameter, read-only shape makes it obvious this is a simple enumeration call. There is no explicit statement of when to prefer this over any alternative or any prerequisite (e.g. admin permissions), though no close sibling alternative exists.

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