Skip to main content
Glama
Sign In
Kaidn-mcp

Kaidn-mcp

Official
by Kaidn-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List scored events

list_events

List scored events for your tenant, newest first. Filter by verdict or event type to narrow fraud investigations.

Instructions

Scored events for this tenant, newest first. Free — does not consume quota. Filter by verdict or event type to narrow an investigation.

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

Input Schema

NameRequiredDescriptionDefault
eventNoEvent type, e.g. 'signup', 'cashout', 'trial_start'
limitNoDefault 25
offsetNo
verdictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the ordering (newest first) and the quota-free nature, but does not mention the return format, pagination behavior, or any other side effects.

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 purpose and key differentiators. No wasted words; every phrase adds value.

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 list tool with no output schema and no annotations, the description covers the core aspects: what is listed, ordering, cost, and filtering use case. Lacks response shape details, but that is often implicit for list tools.

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 50%; event and limit have descriptions, offset and verdict do not. The description adds that verdict and event are filters for investigations, but does not explain offset or pagination semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists scored events for the tenant, with newest first. It provides specific verb and resource, but does not explicitly differentiate from siblings like triage_queue or get_stats.

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?

It gives clear context: the tool is free (does not consume quota) and suggests using filters to narrow an investigation. However, it does not explicitly state when not to use it or mention alternatives.

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