Skip to main content
Glama
Sign In
Kickbacks MCP Server

Kickbacks MCP Server

by Manas8114
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kickbacks_status

Check your Kickbacks.ai connection status and earning state, including authentication, enablement, and hourly/daily cap hits.

Instructions

Get Kickbacks.ai connection status and earning state. Shows whether connected, authenticated, enabled, and if hourly/daily earning caps have been hit. Requires KICKBACKS_API_KEY environment variable.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explains what status fields are returned (connected, authenticated, enabled, caps) and the prerequisite. Lacks mention of rate limits or error behavior but is sufficient for a simple read-only status check.

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 with no redundancy. Front-loaded with purpose and details.

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?

Despite no output schema, description clearly enumerates the status fields. Provides prerequisite. For a zero-parameter tool, this is complete enough.

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?

No parameters exist, so baseline is 4. Description does not need to add param info, and it correctly lists prerequisites instead.

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?

Clearly states the verb 'Get' and the resource 'Kickbacks.ai connection status and earning state'. Lists specific details shown, and distinguishes from sibling tools that deal with history, balance, config, etc.

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

Usage Guidelines3/5

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

Mentions the required environment variable but does not explicitly state when to use this tool versus alternatives like kickbacks_balance or kickbacks_config. Usage context is implied but not directly guided.

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