Skip to main content
Glama

Confirm a work-email code for the one-time400-credit bonus

confirm_credit_bonus
Idempotent

Submit the code from request_credit_bonus. Grants400extra once to an eligible corporate account, never on provider auto-confirmation alone. Personal/free-provider emails receive100base credits. No payment or password change.

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": "confirm_credit_bonus"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code from the authenticated account inbox. Never use another account code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), it discloses the concrete outcome (400 extra, granted once), the eligibility gate (corporate accounts only) and the fallback tier (100 base credits for personal/free-provider emails), plus what it does not touch (payment, password). It does not say what happens with an invalid, expired, or already-used code, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its source, with no filler. Minor damage from fused tokens ('Grants400extra', '100base') that slightly slow parsing but do not obscure meaning.

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 single-parameter, non-destructive, idempotent confirmation tool with no output schema, the description covers source of input, outcome, eligibility, fallback tier, and side-effect boundaries. That is sufficient for an agent to call it correctly.

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 coverage is 100% and the single 'code' parameter already carries a pattern and an inbox-provenance warning, so the description need not explain it. The description's only added value is linking the code to request_credit_bonus as its source, which is helpful but marginal.

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?

States a specific verb and resource ('Submit the code') and immediately anchors it to the sibling that produces that code ('from request_credit_bonus'). An agent can distinguish this from request_credit_bonus without opening either 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 call order is explicit: obtain the code via request_credit_bonus, then submit it here; it also rules out relying on 'provider auto-confirmation alone'. There is no explicit when-not-to-use or expiry/failure guidance, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.