Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

dashboard

Retrieves a partner's summary of accrued, paid, and available amounts plus invited members by member ID.

Instructions

Сводка партнёра: начислено, выплачено, доступно, приглашённые

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": {
      "member_id": "<member_id>"
    },
    "name": "dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, whether it requires partner-level authorization, whether figures are real-time or cached, or how member_id affects the aggregate — all of which matter for a financial summary.

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?

It is a single short phrase with zero redundancy and the key metrics are front-loaded. But it is a noun fragment rather than a structured sentence, and its brevity comes at the cost of the information a caller actually needs.

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?

An output schema exists, so return structure need not be explained. Still, for a financial aggregation tool with one undocumented required identifier and no annotations, the description leaves the identity of member_id, the authorization context, and the freshness semantics entirely unspecified.

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?

There is exactly one required parameter, member_id, with 0% schema description coverage, and the description never mentions it. The agent cannot tell whether member_id identifies the partner whose summary is returned, a specific invited member to filter by, or the calling account, which materially changes the meaning of the result.

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 phrase 'Сводка партнёра' plus the four listed metrics ('начислено, выплачено, доступно, приглашённые') conveys that this returns an aggregated partner summary, which is meaningfully distinct from siblings like 'payouts' or 'referral_status'. However, there is no verb (get, fetch, compute) and no statement of scope, so the agent must infer whether it reads existing data or triggers aggregation.

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 use this tool versus the siblings 'payouts', 'referral_status', or 'status', whose names imply overlapping data. No prerequisites, no exclusions, no mention of when the dashboard is preferable to querying the individual sources.

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