Skip to main content
Glama

get_stats

Retrieve your character's current HP, MP, XP, level, gold, and class from Habitica.

Instructions

Get user stats only (HP, MP, XP, level, gold, class).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:64-68 (registration)
    Tool definition/registration for 'get_stats' in the tools array. Describes that it returns user stats (HP, MP, XP, level, gold, class) with no input parameters.
    {
      name: "get_stats",
      description: "Get user stats only (HP, MP, XP, level, gold, class).",
      inputSchema: { type: "object", properties: {} },
    },
  • Handler function for 'get_stats'. Calls the Habitica API GET /user endpoint and extracts the .data?.stats field from the response, returning it as formatted JSON.
    get_stats: async () => json((await api("GET", "/user")).data?.stats),
Behavior3/5

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

No annotations provided, so description carries full burden. States read-only intent (get stats), but lacks details on response format, auth requirements, or rate limits. Acceptable for a simple read tool.

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?

Single sentence, 11 words, front-loaded with purpose. No unnecessary text.

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 parameterless tool without output schema, description adequately defines what data is returned. Could mention whether result is a single object or array, but still sufficient for basic use.

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?

Tool has zero parameters, so baseline is 4. Description adds no parameter info (none needed). Schema coverage is 100% trivially.

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?

Description clearly states verb 'Get', resource 'user stats', and enumerates returned fields (HP, MP, XP, level, gold, class). Distinguishes from sibling tools like get_user_profile which likely return more data.

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?

Implies use when only those stat fields are needed, but no explicit guidance on when to use vs alternatives like get_user_profile. The word 'only' hints at limited scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leon-jarvis1/habitca_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server