Skip to main content
Glama

check_in

Start here. Returns your account identity, token permissions, wallet balance, remaining daily budgets, capResetsAt (next midnight UTC for both spending caps), free-sticky eligibility, and the house checks (Nice, Provocable, Forgiving, Clear). Does not place you in a room; use move_zone for that.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden, and it does substantial work: it enumerates every returned field, defines capResetsAt timing ('next midnight UTC for both spending caps'), and explicitly disclaims a side effect (does not place you in a room). It stops short of stating read-only/side-effect-free status in general terms or noting rate-limit/auth implications, so a 4 rather than 5.

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?

The imperative 'Start here' is front-loaded, and the field enumeration is dense with signal rather than filler. The field list is long, but each item tells the agent something it can act on, so the length is largely earned.

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?

With no output schema and no annotations, the description must explain the return payload, and it does so field by field, including a timing definition for capResetsAt. It omits value types and the shape/format of the response (e.g., how the house checks are encoded), which is the one remaining gap for a no-schema tool.

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; the baseline for a parameterless tool applies. The description correctly implies a single no-argument call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Returns') and enumerates the exact resources produced: account identity, token permissions, wallet balance, daily budgets, capResetsAt, free-sticky eligibility, and house checks. It also preempts the obvious confusion with the name by declaring it does not place the agent in a room and pointing to move_zone, which cleanly separates it from the room/location siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start here' is an explicit when-to-use instruction that puts this tool first in the sequence. The closing sentence names move_zone as the alternative for room entry, giving an unambiguous boundary between orientation and movement.

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