Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

status

Check service availability, current operating mode, and key presence to verify the partna-mcp connection before managing affiliate program data.

Instructions

Доступность сервиса, режим и наличие ключа

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden and does not meet it. It implies a read-only probe but never states that it is safe, side-effect free, unauthenticated or otherwise, nor does it mention whether a failing key check changes behavior or what 'режим' (mode) actually reflects. The field list restates purpose rather than describing behavior.

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?

A single short phrase with zero padding, and the most important element (service availability) is front-loaded. It is terse rather than wasteful; the only cost is that the brevity leaves terms like 'mode' and 'key' undefined.

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?

An output schema exists, so return values do not need explaining, and the tool is parameterless, which lowers the bar. Still, 'режим' and 'наличие ключа' are unexplained — which key, which service, and what a non-available state means for the caller — leaving an agent unable to fully interpret the result.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs, and the empty schema fully covers the call signature.

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 names three concrete things it reports — service availability, mode, and key presence — which goes beyond the bare tool name 'status'. However, it is a noun phrase with no verb and no indication of which service or scope it covers, so it does not clearly separate itself from siblings like referral_status. Purpose is inferable but not crisply stated.

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 when-to-use guidance at all: no statement of when an agent should call this versus referral_status, dashboard, or claim, and no preconditions. The agent must guess that this is a health/diagnostic probe based on the word 'status' and the field list alone.

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