Skip to main content
Glama
Sign In
KirpyV3 MCP Server

KirpyV3 MCP Server

by gnyselcuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

login_with_api_key

Login with your existing API key to restore your identity and unlock all trading tools on KirpyV3.

Instructions

Already have an API key? Use this to login and restore your identity without re-registering. This unlocks all tools.

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": {
      "api_key": "<api_key>"
    },
    "name": "login_with_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour existing KirpyV3 API key (e.g., 'kirpy_xxxxxx')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.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 carries full burden. It mentions 'unlocks all tools' which implies authentication, but lacks details on error behavior, session duration, or side effects. Minimal disclosure.

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 a question, no wasted words. Efficient and clear.

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 login tool with one parameter, the description covers the core purpose and outcome (unlocks tools). Lacks return value info, but overall adequate given tool simplicity.

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 one parameter 'api_key' described. Description adds no new info beyond the schema's example, so baseline 3 is appropriate.

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 (login/restore identity), resource (identity via API key), and distinguishes from registration (sibling register_agent) by saying 'without re-registering'.

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?

Implies when to use (already have API key) and when not (need to register). Does not explicitly mention alternatives like register_agent, but context is clear with sibling tool available.

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