Dynamoi

Claim Referral Code

dynamoi_claim_referral_code

Destructive

Reserve or change your own referral code. This does not accept referral program terms; the user must accept them on the referral page before joining.

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

Input Schema

Name	Required	Description	Default
`code`	Yes

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`kind`	No
`field`	No
`status`	Yes
`draftId`	No
`message`	No
`retryable`	No
`nextAction`	No
`failureStage`	No
`prerequisite`	No
`screeningResult`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/irreversible framing is covered. The description usefully notes the dependency on terms acceptance happening elsewhere, but does not say what happens to the previous code when changing (invalidated? freed?), whether the operation can fail on an already-taken code, or any uniqueness/format constraints.

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 short sentences, front-loaded with the action and followed by the one precondition that is easy to get wrong. No filler and nothing repeated from the annotations or schema.

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?

An output schema exists, so return values need not be explained. For a destructive, single-parameter mutation, however, the definition leaves the parameter's format/validation rules and the fate of a replaced code unstated, which are the details an agent would most need before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter `code` with 0% schema description coverage, so the description must carry the meaning and largely does not. "Your own referral code" hints that this is the desired/claimed code string, but nothing is said about allowed characters, length, uniqueness conflicts, or whether an existing code is required when changing.

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 gives a specific verb pair and resource ("Reserve or change your own referral code") and scopes it to the caller's own account, which separates it from the read-only dynamoi_get_referrals sibling. It stops short of naming that sibling or clarifying the reserve-vs-change distinction, but an agent can identify the operation 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?

Usage context is clear: it is for reserving a new code or changing an existing one, and an explicit exclusion is provided — it does not accept program terms, which must be handled on the referral page first. There is no explicit routing to alternatives (e.g., get_referrals for viewing an existing code), but the ordering prerequisite is stated.

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

All Dynamoi 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.