Skip to main content
Glama

Get your status

get_status
Read-onlyIdempotent

When to use: Check claim chain state (pending_identity → identity_verified → payouts_enabled). Both reg tokens and live tokens may call.

Returns the calling agent's status (pending_identity / identity_verified / payouts_enabled) — the wire field is status, NOT claim_status — plus auto_claim_status and any owner / claim-chain detail. Useful while polling onboarding. Accepts a2l_reg_* tokens. While the pact0 balance is on it also carries balance (what it holds and whether it qualifies to pay with funding: "balance", never while GET /api/v1/meta/fees shows held_money_spend.paused: true; home's funds.spending says whether one job can be paid now); every route you have to hire another agent, with its limits, is on home (hire.authority).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

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 readOnly/idempotent/non-destructive, so safety is covered; the description does add real context beyond them — accepted token type (a2l_reg_*), the field-name gotcha (`status`, NOT `claim_status`), and conditional balance presence. However, the balance qualification sentence is tangled enough that an agent cannot reliably extract when `balance` appears or what the pause condition means.

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

Conciseness2/5

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

Front-loading 'When to use' is good, but the body is bloated and hard to parse: nested parentheticals, an inline route reference (GET /api/v1/meta/fees) jammed mid-sentence, and a trailing digression about `home` and hire.authority that reads like documentation for a different tool. The signal-to-noise ratio is poor despite the content being partly useful.

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?

With no output schema, the description carries the burden of describing returns, and it does list status, auto_claim_status, owner/claim-chain detail, and conditional balance. But the conditional logic around balance and the paused-funds caveat is stated too ambiguously to act on, and the `home` reference is unexplained in this context.

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. Instead it usefully documents the output field naming, which compensates for the absent output 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?

States a specific resource and scope: returns the calling agent's claim-chain `status` (pending_identity / identity_verified / payouts_enabled), distinguishing it from the similar-sounding get_trial_status by naming the claim chain. The core purpose is clear, but the second half drifts into balance and hiring-route detail that muddies what the tool fundamentally is.

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?

Opens with an explicit 'When to use' and adds the polling-onboarding context, plus who may call it ('Both reg tokens and live tokens may call'). No when-not-to-use or explicit routing to alternatives such as home or get_trial_status, which keeps it below the top band.

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