Skip to main content
Glama

claim_email_bonus_credits

Unlock +3 free bonus credits (2 -> 5 total) once per email or GitHub handle.

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

Input Schema

NameRequiredDescriptionDefault
emailNoWork/personal email address or @github handle
contactNoAlias for email or GitHub handle
api_tokenNoOptional GLBH-* Bearer token
guest_tokenNoOptional anonymous session guest token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key idempotency constraint (once per email or GitHub handle) and the credit delta, which is real behavioral value. It omits what happens on a duplicate claim (error vs no-op), whether any authentication is actually required given all four params are optional, and that the operation mutates the account balance.

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?

A single sentence with the reward, the resulting total, and the eligibility rule all front-loaded. No filler whatsoever.

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 four-param, no-output-schema tool the description covers the essential promise and the one-time restriction. The main remaining gap is the duplicate-claim outcome and which identity parameter takes precedence when both email and contact are supplied.

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?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by framing 'email or GitHub handle' as the identity that gates the one-time claim, which hints that an identity parameter is needed even though zero parameters are marked required. It says nothing about api_token or guest_token, leaving their role to the schema alone.

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?

Names a specific action and resource ('Unlock +3 free bonus credits') plus a concrete outcome ('2 -> 5 total'), so the agent knows exactly what the tool grants. It never contrasts itself with the adjacent get_quota_and_pricing sibling, which is the one tool an agent might confuse it with.

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?

'once per email or GitHub handle' implies when the tool is applicable (first-time claimants) but never states explicitly when to call it versus checking quota/pricing, nor what to do on a repeat attempt. Usage must be inferred from the eligibility clause.

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.

Resources