Skip to main content
Glama

Whizbrew

Make the account your human's

claim

Two small steps. 1: {email} of your human gives a short link; they open it, confirm the email, and the page shows an 8-letter code. 2: {code} they read to you makes the account theirs for good, with its key and balance. Free.

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

Input Schema

NameRequiredDescriptionDefault
codeNoStep 2: the 8-letter code the page showed your human
emailNoStep 1: the email that should own the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, non-open-world call. The description adds critical context beyond that: it requires out-of-band human action, it is two-phase, and the effect is permanent ('for good') and transfers a key and balance. It still says nothing about failure modes (wrong or expired code) or what is returned.

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?

Roughly two sentences, front-loaded with the numbered steps, and 'Free.' carries real information about cost. The phrasing is telegraphic in places ('{email} of your human gives a short link'), which slightly slows parsing but adds no padding.

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?

The tool is simple (2 optional-string params, no output schema), and the description covers the flow and prerequisites well. However, with no output schema it never says what a successful claim returns or what 'key' refers to, and it omits error handling, leaving a real gap for an agent driving a multi-step human-in-the-loop process.

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, but the description earns more by situating each parameter in the workflow: email is step 1 and drives the link, code is the 8-letter value shown after confirmation. It clarifies the relationship between the two inputs rather than just restating the schema.

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 states a concrete two-step outcome: the human confirms an email, then reads back an 8-letter code so the account becomes 'theirs for good, with its key and balance.' That is a specific verb-and-resource result an agent can grasp. It does not compare itself against siblings such as 'start' or 'add_money', so it falls short of a 5.

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?

The text spells out the required sequence (get link -> human confirms -> human reads code -> call with code), which is genuine procedural guidance and implies when the tool applies. There is no explicit when-not guidance, no mention of what to do if the human never confirms, and no comparison to any alternative tool.

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