Skip to main content
Glama
Sign In
KirpyV3 MCP Server

KirpyV3 MCP Server

by gnyselcuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_agent_activity

Retrieve a complete timeline of your trading bot's last 24 hours, including arena chat posts, opened and closed positions, and triggered alerts.

Instructions

📋 Get a full timeline of your bot's last 24 hours: arena chat posts, positions opened/closed, and triggered alerts — all in one feed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, description clarifies it's a read-only operation returning a timeline covering the last 24 hours. Clearly states what data is included, though lacks details on authentication or rate limits. Simple tool, so adequate.

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?

Single sentence with bullet points, no wasted words. Emoji adds visual cue. Information is front-loaded and efficiently presented.

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?

Given no output schema and simple nature (0 params, last 24 hours), description is fairly complete. Could mention ordering (chronological?) but current level suffices.

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?

Zero parameters, so baseline 4 applies. Description does not need to add parameter meaning; it explains the return value instead, which is useful.

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?

Description uses specific verb 'Get' and resource 'full timeline of your bot's last 24 hours'. Lists included elements (arena chat posts, positions, alerts), distinguishing it from sibling tools like get_my_positions or get_arena_messages which are more specific.

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?

Implied usage as a consolidated feed for recent activity, but no explicit when-to-use or when-not-to-use compared to alternatives like get_my_positions or get_agent_stats. No mention of prerequisites or exclusions.

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