Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create API key

create_api_key
Destructive

Create a new API key for Stables API access; save the secret immediately because it is shown only once.

Instructions

Create a new API key for accessing the Stables API. The secret key is only shown once on creation - save it immediately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA descriptive name for this API key (e.g., 'Production Bot', 'Agent Smith')
metadataNoOptional metadata to attach to the key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / metadata / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv1.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the write/irreversibility profile is covered. The description adds a genuinely non-obvious operational fact not present in any structured field: the secret is displayed only once and must be saved immediately. It still omits what permissions/scope the created key carries and whether creation requires elevated auth.

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?

Two sentences, no waste, with the one-time-secret warning front-loaded right after the purpose statement where an agent will not miss it.

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?

No output schema exists, and the description compensates by telling the agent that the secret is returned exactly once — arguably the single most important return-value fact. For a simple 2-param creation tool this is close to complete; only key scope/permission semantics are unaddressed.

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% and the name param even carries examples, so the schema does the heavy lifting. The description adds no meaning about `name` or the optional nested `metadata` map, which is the baseline 3 case.

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+resource ('Create a new API key') and scopes it to the Stables API, so it is distinguishable from list_api_keys/get_api_key/revoke_api_key in the sibling set. It never explicitly names or contrasts those siblings, so it stops short of a 5.

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 by the verb — the agent can infer this is the way to mint a key, but there is no explicit 'use this when...' framing, no mention of when to rotate/revoke instead, and no prerequisite (auth/permission) guidance.

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