Skip to main content
Glama
Sign In
Kaidn-mcp

Kaidn-mcp

Official
by Kaidn-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Review queue, highest risk first

triage_queue

Retrieve events with a review verdict sorted by score descending, so you can handle high-risk fraud cases first in your daily triage queue.

Instructions

Every event sitting on the 'review' verdict, sorted by score descending — the daily triage job. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It specifies the filter and sort, indicating a read-only query. However, it doesn't disclose the effect of the limit parameter (the description says 'every event' but limit can restrict results), and 'Free' is ambiguous. No contradictions with annotations (none present).

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?

One sentence, highly efficient, front-loaded with the core behavior. The final 'Free' note is extraneous but not harmful.

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 simplicity (one optional param, no output schema), the description covers the main purpose. However, it fails to reconcile 'every event' with the limit parameter, and does not describe the return format or potential pagination. The lack of annotations and output schema places more burden on the description, but it still provides a sufficient overview for a basic list tool.

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?

The schema covers 100% of the single parameter with a description (though minimal: 'Default 50'). The property name is self-explanatory, so baseline 3 applies. The tool description adds no parameter details.

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 states the tool's function: returns events with 'review' verdict, sorted by score descending. It distinguishes from sibling tools like list_events by specifying the filter and sort order. The title reinforces this.

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?

The description provides clear context (daily triage job) and implies this is the tool for reviewing high-risk events. However, it doesn't explicitly mention alternatives or when not to use it, preventing a 5.

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