Skip to main content
Glama
Sign In
wealify-kpi-mcp

wealify-kpi-mcp

by ngkienmkqn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kpi_overview

Generate a quarterly company-wide KPI overview including per-squad performance, sales leaderboard, chapter averages, and engine-3 status. Ideal for CEO and Finance digests.

Instructions

Company-wide overview for a quarter: per-squad performance, sales leaderboard, chapter averages, engine-3 status. Use for CEO/Finance digests.

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

Input Schema

NameRequiredDescriptionDefault
quarterNoQuarter 'QX/YYYY' — defaults to current

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It implies a read operation but does not explicitly state read-only, permissions, rate limits, or side effects. It lacks transparency about what the tool does beyond returning data.

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?

Two concise sentences: the first summarizes contents, the second gives usage context. No redundant information, perfectly 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?

For a simple 1-parameter tool with no output schema, the description adequately conveys the scope and use case. It doesn't cover error behavior or output format, but these are less critical for an overview tool.

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 coverage is 100% with a clear description of the quarter parameter. The description does not add any extra meaning beyond the schema, which meets the baseline expectation.

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?

Description specifies a specific verb+resource (overview of KPIs) and lists contents: per-squad performance, sales leaderboard, etc. It distinguishes from siblings by stating 'company-wide overview' and targets a specific audience (CEO/Finance).

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

Usage Guidelines4/5

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

Clearly states when to use: 'Use for CEO/Finance digests.' However, it does not explicitly exclude alternatives or mention when not to use, given many sibling tools exist.

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

Deploy Server

Other Tools