Skip to main content
Glama
kuyen-labs

Fuul MCP Server

by kuyen-labs

check_event_status

Check the ingestion and downstream pipeline status of an event, including trigger executions, attributions, payouts, and movements.

Instructions

Check event ingestion and downstream pipeline. Default (verbose omitted or false): GET /api/v1/events/status with user_identifier, user_identifier_type, event_name → {"created":true|false}. verbose=true: GET /api/v1/events/pipeline — returns event, trigger_executions (status, status_details), attributions, payouts, movements. Requires event_id OR dedup_id + event_name (same dedup_id/name as send_event). Poll every 2–5s after send_event until attributions/payouts appear. 404 → {"created":false}. Auth: project API key only (pass project_api_key or set env FUUL_MCP_PROJECT_API_KEY). Dashboard OAuth from fuul-mcp login is not accepted on these routes. Rate limit: 100 requests/minute. If the API returns HTTP 429, wait Retry-After seconds (if present) before retrying. Example status: {"user_identifier":"0x...","user_identifier_type":"evm_address","event_name":"trade"}. Example verbose: {"verbose":true,"dedup_id":"swap-123","event_name":"trade"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_api_keyNoProject API key used as Bearer for this request. Falls back to FUUL_MCP_PROJECT_API_KEY when omitted.
verboseNoWhen true, returns full downstream pipeline (trigger executions, attributions, payouts, movements).
user_identifierNo
user_identifier_typeNo
event_nameNoCase-sensitive trigger name.
event_idNoEvent UUID. Use with verbose instead of dedup_id + event_name.
dedup_idNoDedup id from send_event. Required with event_name when verbose and event_id omitted.
Behavior5/5

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

No annotations, so description carries full burden. Discloses two endpoints based on verbose flag, parameter combinations, auth method (project API key only, no OAuth), rate limit of 100/min, retry-after behavior, and response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with front-loaded purpose, but slightly verbose. All information is necessary, though could be tightened. Still highly readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 7 parameters, description covers all parameter combinations, auth, rate limits, error handling, polling advice, and examples. Extremely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

71% schema coverage but description adds critical context: explains dependency of verbose on event_id or dedup_id+event_name, clarifies user_identifier fields for non-verbose, and provides examples. Adds significant meaning beyond schema.

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 clearly states 'Check event ingestion and downstream pipeline', distinguishes between verbose/non-verbose modes, and specifies API endpoints and required parameters. This distinguishes it from sibling tools like send_event.

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?

Provides explicit polling guidance after send_event, parameter requirements, authentication (project API key only), rate limits, and error handling (404/429). Lacks explicit 'when not to use' but context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuyen-labs/mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server