DevHelm MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create_api_key

Create an API key with a human-readable name and optional expiration date. The key value is displayed once at creation for immediate use.

Instructions

Create a new API key. The key value is returned only once.

Required fields: name. Optional: expiresAt.

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": {
      "body": "<body>"
    },
    "name": "create_api_key"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2May 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the key value is returned only once, which is a critical behavioral trait. However, it omits other important aspects such as whether the key is immediately active, permissions required, or what happens on failure.

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 extremely concise: two sentences with no redundant information. Every word is necessary and contributes to understanding the tool's purpose and key behavioral note.

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

Completeness3/5

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

Given the presence of an output schema, the description does not need to detail return values, but it could mention that the key value is part of the response. There is no discussion of prerequisites, error states, or related operations, leaving some gaps for a creation tool.

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 already contains detailed descriptions for both parameters (name and expiresAt). The description simply restates that name is required and expiresAt is optional, adding minimal value beyond the schema. With high schema description coverage, a score of 3 is appropriate.

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?

The description clearly states the tool creates a new API key, with a specific note that the key value is returned only once. This is a direct verb-resource statement that distinguishes it from other API key management tools like revoke_api_key or delete_api_key.

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?

The description implies when to use this tool (when a new API key is needed) but does not provide explicit guidance on when not to use it or alternatives among sibling tools. The one-time return note is a helpful hint for post-creation behavior but does not serve as a usage guideline.

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

Deploy Server