Plain Insurance

Confirm the signup email

verify_onboarding_email

Confirms the signup email with the eight-digit code the person received. Codes expire after 15 minutes and allow five attempts. Keep the returned capability and continuationToken private. Does not activate insurance.

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": {
      "onboardingId": "<onboardingId>",
      "capability": "<capability>",
      "code": "<code>"
    },
    "name": "verify_onboarding_email"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	The eight-digit code from the verification email. Valid for 15 minutes, five attempts.
`capability`	Yes	From the /start result.
`onboardingId`	Yes	From the /start result.

Output Schema

Name	Required	Description
`state`	Yes	awaiting_verification: ask the person for the emailed code; email_confirmed: call /verify-email again to finish; verified: offers are ready.
`policyIds`	Yes	IDs of the offered policies, once created.
`capability`	Yes	Secret proof of this signup. Keep it private and send it with onboardingId.
`onboardingId`	Yes	Identifies this signup.
`continuationToken`	No	Secret token for /payment-handoff, valid for 15 minutes after verification.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: codes expire after 15 minutes, only five attempts are allowed, returned capability and continuationToken must be kept private, and the tool does not activate insurance. These details materially help an agent understand security, retry limits, and side-effect boundaries.

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 four short sentences, front-loads the core action, and every sentence adds useful information. There is no redundant or filler wording.

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?

The tool has three required parameters, an output schema, and annotations covering safety hints. The description adds the key behavioral context an agent needs, though it could be more complete by explicitly naming prerequisites or alternatives among sibling tools.

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%, so all three parameters are already documented in the schema. The description reinforces the eight-digit code format and expiry/attempt limits, but it does not add meaning beyond the schema for onboardingId or capability.

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?

The description states a specific verb and resource: it confirms the signup email using an eight-digit code. This is clear enough for an agent to identify the operation, but it does not explicitly distinguish this tool from siblings such as create_onboarding or get_onboarding_payment_link.

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 after the person receives a code and adds constraints such as 15-minute expiry and five attempts. However, it does not explicitly say when to call this tool versus the sibling onboarding tools, nor does it state prerequisites like having already called create_onboarding.

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

All Plain Insurance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?