Code-Fundi MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

code-fundi-auth-resend

Resend the OTP email for a new account when the previous code expired or wasn't received. Call it after authentication and before verification.

Instructions

Resend the OTP email (POST /v2/auth/resend) when the previous code expired or was not received. Use after code-fundi-auth-authenticate, before code-fundi-auth-verify. Default type is signup for new accounts.

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": {
      "email": "<email>"
    },
    "name": "code-fundi-auth-resend"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Resend type (default: signup)
`email`	Yes	Email address to resend the code to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations only include readOnlyHint: false, so the description carries some burden. It adds the POST method and default type context, but does not disclose potential side effects (e.g., sending an email, rate limits) or error behaviors. The added flow information is useful but not deeply behavioral, so a moderate score is appropriate.

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 concise, with three sentences that each serve a distinct purpose: what the tool does, when to use it, and a key parameter default. It is front-loaded with the action and contains no filler or redundant information.

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?

For a simple tool with two parameters and no output schema, the description covers purpose, usage timing, and parameter default sufficiently. It lacks details on failure modes or response handling, but given the simplicity and schema coverage, it is nearly complete.

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 already includes the default for 'type' ('signup') and the purpose of each parameter. The description's mention of default type is redundant with the schema, so it adds no additional meaning beyond what is already structured.

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's function with a specific verb ('Resend') and resource ('OTP email'), and includes the endpoint. It also differentiates from siblings by placing it within the auth flow ('after authenticate, before verify'), making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly specifies when to use the tool ('when the previous code expired or was not received') and gives sequencing instructions relative to sibling tools ('Use after code-fundi-auth-authenticate, before code-fundi-auth-verify'). This provides clear guidance on placement in the workflow.

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