Skip to main content
Glama

Request the optional work-email bonus code

request_credit_bonus

Send one email code to the authenticated account address to qualify for400additional credits (500total). Base100credits are already usable; this step is optional. Does not accept an arbitrary recipient. No credits charged. If the bonus is already claimed, returns its state without another email.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "request_credit_bonus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the recipient is fixed to the authenticated account, that no credits are charged, and what happens in the already-claimed case. These are real behavioral facts not present in the structured fields. Minor tension: the already-claimed short-circuit reads as idempotent for settled claims, while idempotentHint=false suggests repeat sends are possible in the unclaimed case — the description does not resolve that.

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

Conciseness3/5

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

The intent is front-loaded and no sentence is superfluous, but the text is marred by broken token spacing ('for400additional credits (500total)', 'Base100credits'), which slows parsing. A short, clean rewrite would score higher.

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 zero-parameter tool with no output schema, the description covers purpose, cost, recipient constraint, and the already-claimed outcome. It does not say what the returned state looks like or what happens if the send fails, but the essentials for correct invocation are present.

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

Parameters4/5

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

There are zero parameters, which sets the baseline at 4. The description still earns its place by explaining that no recipient argument is accepted, so an agent will not waste a call trying to pass an address.

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?

States a specific verb and resource: 'Send one email code to the authenticated account address to qualify for 400 additional credits'. An agent can tell this is the request half of a bonus flow. It does not explicitly name the sibling that consumes the code (confirm_credit_bonus), so sibling differentiation is only implied.

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?

Gives clear conditions: 'this step is optional', 'Does not accept an arbitrary recipient', and 'If the bonus is already claimed, returns its state without another email'. That covers when-not-to-expect-a-new-email. It never names the follow-up confirmation tool, so the next step must be inferred.

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.