Motomarks MCP Server

Complete Motomarks sign-up

complete_sign_up

Verify the six-digit email code from sign_up. Creates the account when the email is new, then returns API keys so the client can reconnect as that user.

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>",
      "code": "<code>"
    },
    "name": "complete_sign_up"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	Six-digit verification code from the email.
`email`	Yes	The same email address passed to sign_up.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the verification step, the conditional write side effect ('Creates the account when the email is new'), and the return contract (API keys). It omits failure/edge-case behavior (invalid code, existing email), but the core side effects are transparent.

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 tightly written sentences with no filler. The primary action is front-loaded, and the second sentence efficiently adds the condition and the return value. Every clause contributes meaning.

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 two-parameter flow with no output schema, the description covers the purpose, input relationship, key side effect, and what the caller receives (API keys). It does not specify the exact shape of the returned keys or error behavior, but these are not essential for invoking the tool in the primary success path.

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 both parameters are already documented in the input schema. The description adds only the contextual link that the email came from sign_up, which is useful but does not materially expand parameter semantics beyond the schema. Baseline 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 identifies a specific verb and resource ('verify the six-digit email code', 'creates the account', 'returns API keys') and clearly distinguishes this from the sibling sign_up tool by positioning it as the completion step. An agent can tell exactly what this tool does without opening the schema.

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

Usage Guidelines4/5

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

The phrase 'from sign_up' establishes clear two-step flow context, and 'when the email is new' gives a conditional usage boundary. It does not explicitly list when not to use it or alternative tools, but for a sign-up completion step the implied usage is clear enough.

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

All Motomarks MCP Server 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.