Skip to main content
Glama

get_user_stats

Retrieve collection, activity, achievement, and rating statistics for your profile or another public profile; add a year and optional month to include that period’s recap.

Instructions

Collection, activity, achievement and rating statistics for you (default) or another public profile. year (and optional month) adds that period's recap.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
monthNo
usernameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two useful behaviors: the default target is the caller's own profile, and other targets must be public profiles. It does not state access/auth requirements, error behavior for private or non-existent profiles, or that the call is read-only.

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?

Two short sentences, front-loaded with the returned data categories before the scoping and period modifiers. Dense and mostly free of waste, though the phrasing is slightly compressed to the point of terse ambiguity.

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?

An output schema exists, so return-value detail is not required, and the tool takes only three optional parameters. The remaining gap is the unspecified string formats and the month-without-year interaction, which an agent calling this tool would want to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate; it adds meaning for username (another public profile) and for year plus optional month (that period's recap). It omits value formats for year/month, what an empty string default means, and whether month is valid without year.

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 (collection, activity, achievement and rating statistics) and a default scope ("for you (default) or another public profile"). This lets an agent distinguish it from the game-scoped sibling get_game_stats, though that contrast is never made explicit.

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 default-to-self behavior and the period-recap behavior implied by year/month give some usage context. However, there is no statement of when to prefer this over get_game_stats or other stats-related siblings, and no prerequisites are described.

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