Skip to main content
Glama

get_user_profile

Retrieve the complete profile of the authenticated Habitica user, including stats, preferences, inventory, party details, and other account data.

Instructions

Get the authenticated user's full profile (stats, prefs, items, party, etc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:59-63 (registration)
    Tool registration in the `tools` array defining the tool's name, description, and input schema.
    {
      name: "get_user_profile",
      description: "Get the authenticated user's full profile (stats, prefs, items, party, etc).",
      inputSchema: { type: "object", properties: {} },
    },
  • Input schema for get_user_profile: no parameters required.
      inputSchema: { type: "object", properties: {} },
    },
  • Handler that makes a GET request to /user endpoint and returns the full user profile data.
    get_user_profile: async () => json((await api("GET", "/user")).data),
  • Helper function `json` used by the handler to format the response as pretty-printed JSON.
    const json = (obj) => ok(JSON.stringify(obj, null, 2));
  • Helper function `ok` that wraps text into the MCP content response format.
    const ok = (text) => ({ content: [{ type: "text", text }] });
Behavior4/5

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

With no annotations, the description carries full burden. It implies a read-only operation via 'Get' and mentions the broad scope of the profile. No side effects are indicated, which is acceptable for a straightforward retrieval 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 with 10 words, no redundant information. Every part is meaningful and front-loaded.

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?

No output schema exists, but the description lists the profile components (stats, prefs, etc.), giving sufficient context for a simple getter. The tool is straightforward with no parameters.

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?

Input schema has zero parameters and 100% schema description coverage. The description adds no parameter info, which is appropriate since there are no parameters to document.

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 clearly specifies the verb 'Get' and resource 'authenticated user's full profile', and lists included parts (stats, prefs, items, party). It distinctly differentiates from sibling tools that focus on specific items or tasks.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, the context of sibling tools and the generic nature of fetching a full profile makes the usage relatively obvious.

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