Skip to main content
Glama
wakapi-mcp

wakapi-mcp

by si-essence

wakapi_leaderboard

Read-only

List Wakapi leaderboard rankings to compare coding-time statistics across users.

Instructions

wakapi_leaderboard covers the leaderboard toolset (1 operations). Calls go to WAKAPI_URL with the /api prefix. Authenticated routes send Authorization Basic base64 of the API key. The key is never placed in the URL. Health and shields badges send no key. action help with target returns one action's parameters. Actions: list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "wakapi_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON object or JSON array. Secrets are redacted in output.
queryNoQuery parameters, such as from, to, project, language, and date. Summaries accept format csv.
actionYesWakapi operation to call, or help.
paramsNoPath parameters, such as user, range, interval, filter, and id.
targetNoWith action help, the action whose parameters to describe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful context about auth (Basic base64 API key, key never in URL) and transport (WAKAPI_URL with /api prefix), but this reads as shared boilerplate and says nothing tool-specific such as result ordering, pagination, or date-range defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description leads with a meta-summary ('covers the leaderboard toolset (1 operations)') rather than the useful content, and includes a sentence about health and shields badges sending no key that is irrelevant to a leaderboard tool. The auth and action sentences do earn their place, but the overall text is templated and not front-loaded for this operation.

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?

With no output schema, the description should convey what a call returns, but it never describes the leaderboard payload, ordering, or how date-range query parameters affect results. It is adequate for invoking the tool (one action, documented params) but leaves the agent guessing about the response shape.

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 100% and all five parameters carry descriptions, including the from/to/project/language/date hints on query and the target parameter for help. The description adds no additional meaning beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

The description states the resource ('leaderboard toolset') and enumerates the single available action ('list'), so an agent can infer it lists leaderboard entries. However, it never says what a leaderboard contains here (e.g. users ranked by coding time) and offers no differentiation from siblings like wakapi_summaries or wakapi_projects beyond the tool name itself.

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?

There is no guidance on when to call list versus wakapi_summaries or wakapi_projects, nor any prerequisites or exclusions for this tool. The only usage note is procedural ('action help with target returns one action's parameters'), which explains the help action but not the actual operation.

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