Skip to main content
Glama
wakapi-mcp

wakapi-mcp

by si-essence

wakapi_projects

Read-only

List and retrieve Wakapi project data to inspect coding-time analytics, with query filters for date range, project, language, and CSV output.

Instructions

wakapi_projects covers the projects toolset (2 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, get.

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_projects"
  }
}

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.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds useful authentication context about Basic auth and API-key placement, but it does not describe return behavior, pagination, errors, or what list/get actually produce; the health/shields badge note is also largely irrelevant here.

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 scope is front-loaded, but the description is a series of fragmented implementation notes. Details about health and shields badges and API-key placement are not central to invoking project operations and reduce focus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-action tool with five parameters and no output schema, the description leaves important operational gaps. It explains auth and the help action, but not what list or get return, which path parameters they require, or how an agent should choose between them.

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%, so the schema already documents action, body, query, params, and target. The description adds little beyond clarifying that help with target returns one action's parameters and that requests use Basic auth; it does not deepen meaning for the query or path parameter fields.

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 states that this tool covers the Wakapi projects toolset and names its operations: list and get. That gives a clear verb/resource connection, though it does not explain how projects differ from sibling resources such as heartbeats or summaries.

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?

It lists the available actions but gives no guidance on when to choose list versus get, or when to use this tool instead of sibling tools. The only routing guidance is for the meta help action, not for the core project operations.

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