Skip to main content
Glama
Sign In

Codestats

by io.github.pipeworx-io
OverviewDiscussionsAdmin

User

user
Read-onlyIdempotent

Public profile — total XP, per-language XP, per-machine XP.

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": {
      "username": "johndoe"
    },
    "name": "user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Output Schema

NameRequiredDescriptionDefault
userNo
machinesNoXP breakdown by machine
languagesNoXP breakdown by programming language

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "username": "johndoe"
+  },
+  {
+    "username": "alice_dev"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "languages": {
+      "description": "XP breakdown by programming language",
+      "items": {
+        "properties": {
+          "language": {
+            "description": "Programming language name",
+            "type": "string"
+          },
+          "xp": {
+            "description": "XP earned in this language",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "machines": {
+      "description": "XP breakdown by machine",
+      "items": {
+        "properties": {
+          "machine_name": {
+            "description": "Name of the machine",
+            "type": "string"
+          },
+          "xp": {
+            "description": "XP earned on this machine",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "user": {
+      "properties": {
+        "total_xp": {
+          "description": "Total XP earned across all languages",
+          "type": "integer"
+        },
+        "username": {
+          "description": "Username of the Code::Stats user",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety semantics are covered. The description adds meaningful context: the profile is 'public' and the exact XP fields returned. This goes beyond the structured annotations.

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 description is a single, efficient line with no redundant words. However, it is a fragment and could benefit from a verb to clarify the action. It is appropriately sized but slightly under-specified.

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?

The tool is simple (one parameter) and has an output schema, so return format is already covered. The description conveys the core data content, but lacks usage guidance and any connection to the input parameter, making it only partially complete.

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

Parameters2/5

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

The schema has one required 'username' parameter with no description, and schema description coverage is 0%. The description does not mention the parameter or explain how the username is used, leaving the agent to rely on the parameter name alone.

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?

The description clearly identifies the tool as returning a public profile with XP breakdowns (total, per-language, per-machine). Although it lacks an explicit verb, the intent is evident. It differentiates from siblings like entity_profile by focusing on user-specific XP data, though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description only states what the profile contains, without mentioning scenarios, prerequisites, or exclusions. There is no 'use this when' or 'instead of' context.

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

All Codestats toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources