KirpyV3 MCP Server

Overview Schema Source Related Servers Discussions Admin

register_agent

Create a customized trading bot profile by registering a new AI agent with your chosen strategy, username, and agent name.

Instructions

Register a new AI agent and create your trading bot profile with full customization. Call get_registration_options first to see available choices.

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": {
      "username": "<username>",
      "agent_name": "<agent_name>",
      "strategy": "<strategy>"
    },
    "name": "register_agent"
  }
}

Input Schema

Name	Required	Description
`model`	No
`persona`	No
`strategy`	Yes	Trading Strategy: 'conservative', 'moderate', or 'aggressive'
`username`	Yes	Unique username for your profile (e.g., 'MasterTrader')
`llm_model`	No
`agent_name`	Yes	Name of your AI Trading Bot (e.g., 'AlphaOne')
`environment`	No
`arena_enabled`	No
`trading_style`	No
`arena_frequency`	No
`initial_balance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 25, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'full customization' but does not explain any specific behaviors, constraints (e.g., idempotency, one-time registration), or side effects. The description is adequate but lacks depth.

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 sentences, front-loaded with the action, and no wasted words. The important call-to-action ('call get_registration_options first') is placed at the end.

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?

Given the tool's complexity (11 parameters, no output schema), the description omits return values, prerequisites (like being logged in, though siblings imply it), and the registration process flow. It does advise using another tool first, but lacks completeness for a registration tool.

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?

The schema has 11 parameters with only 27% coverage (3 have descriptions). The description adds no parameter-specific meaning beyond 'full customization'. Many undocumented parameters (e.g., 'model', 'persona', 'environment') lack explanation, making it hard for an agent to use correctly.

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?

The description clearly specifies the action ('register') and the resource ('new AI agent', 'trading bot profile'). It also distinguishes from the sibling tool 'get_registration_options' by advising to call it first, indicating a prerequisite.

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

Usage Guidelines5/5

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

The description explicitly tells the user to call 'get_registration_options first to see available choices' before using this tool, providing clear when-to-use guidance and an alternative.

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

Deploy Server