Code-Fundi MCP Server

Official

by Code-Fundi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

code-fundi-regenerate-api-key

Destructive

Regenerate your Code-Fundi API key. The new key appears once and is automatically applied to all future tool calls.

Instructions

Regenerate the Code-Fundi API key. The full key is shown only once. The new key is automatically configured for all subsequent tool calls.

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": "code-fundi-regenerate-api-key"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds valuable behavioral context: the key is shown only once and is automatically configured for subsequent calls. This warns the user about key recovery and broader impact, going beyond the annotation without contradicting it.

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, front-loaded with the primary action. The second sentence provides essential caveats without waste. Every word earns its place.

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?

For a simple zero-parameter tool with annotations and no output schema, the description fully covers the purpose, the irreversible nature of the action, and the automatic reconfiguration effect. Nothing critical is missing.

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 has zero parameters, and the schema coverage is 100% (empty schema). Per guidelines, a baseline of 4 is appropriate since there are no parameter semantics to clarify.

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 action: 'Regenerate the Code-Fundi API key.' It uses a specific verb and resource, distinguishing it from sibling tools like list-api-keys and disable-api-key. The purpose is unambiguous.

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 usage (when you need a new API key) but does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The caveat 'full key is shown only once' hints at caution but lacks explicit guidance.

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