Skip to main content
Glama

Whizbrew

Where this account stands

start
Read-only

Says whether this account is still an agent's (not claimed: it stops after 7 days) or a person's, its balance, and the one next step. An agent without a key starts over HTTP: POST /v1/agent/start (no email). 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": "start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond the schema: the unclaimed status expires after 7 days, the call is free, and a keyless agent must bootstrap over HTTP instead.

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?

Two sentences with no filler, but the opening clause ("whether this account is still an agent's ... or a person's") is grammatically awkward and forces a re-read before the actual purpose lands.

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, no-output-schema status tool, the description covers returns, cost, the 7-day expiry, and the keyless bootstrap path. Nothing essential to invoking it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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?

"Says whether this account is still an agent's ... or a person's, its balance, and the one next step" names concrete outputs (ownership status, balance, recommended action), so an agent can predict the response. It stops short of distinguishing the tool from siblings like get_balance, which returns overlapping information, and the name "start" is not reconciled with what is actually a status read.

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 clause "An agent without a key starts over HTTP: POST /v1/agent/start (no email)" is a real routing exclusion — it tells keyless agents not to use this tool — but there is no guidance on when to prefer this over get_balance or claim.

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