Skip to main content
Glama

klanex

by io.github.chrassy

execute

Submit an HTTP call to a third-party API for reliable asynchronous execution. klanex validates the payload (optionally against payload_schema), stores credentials encrypted, executes with automatic retries/backoff/circuit breakers, and keeps an audit trail — you submit once and never retry transient failures yourself.

Call this instead of making a direct HTTP request whenever the call has side effects (payments, messages, tickets, writes) or the target may be flaky. Prefer connection_id over headers for credentials. Always set idempotency_key for side-effecting calls so resubmitting can never double-execute. Set wait_seconds to block for the result; otherwise poll get_execution with the returned execution_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesabsolute http(s) URL of the target endpoint
methodNoHTTP method: GET, POST, PUT, PATCH, or DELETE (default POST)
headersNorequest headers, typically third-party credentials; encrypted at rest and never readable back. Prefer connection_id so secrets never pass through your context
payloadNoJSON body to send to the target
seal_urlNoset true when the URL itself is a secret (webhook URL, presigned URL); it is encrypted and reads back redacted
timeout_msNoper-attempt timeout in milliseconds (default 30000)
max_attemptsNomaximum delivery attempts, 1-10 (default 5)
wait_secondsNoblock up to this many seconds (max 55) for a terminal result instead of returning immediately after queueing
connection_idNoID of a stored credential connection (con_...) to authenticate the call; see list_connections
payload_schemaNoJSON Schema to validate payload against before anything executes; mismatches are rejected synchronously with a correction hint
idempotency_keyNostable key (max 255 chars) making this submit safe to retry; the same key returns the original execution instead of creating a new one. Always set this for side-effecting calls
requires_approvalNopause for a human approve/reject decision before anything executes; use for destructive or high-stakes actions

TDQS

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description thoroughly discloses behavior: validates payload optionally, stores credentials encrypted, automatic retries/backoff/circuit breakers, audit trail, idempotency, approval pause, and blocking wait. This covers all critical behavioral traits.

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 paragraphs: first explains the tool's core capability and guarantees, second provides actionable usage guidelines. No superfluous words, every sentence 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?

Given 12 parameters and no output schema, the description covers all major aspects: validation, security, reliability, polling. It mentions returning an execution_id but could explicitly state what the output looks like. However, the behavioral context is rich enough for an agent to use the tool effectively.

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?

Schema coverage is 100%, so baseline 3. Description adds significant value by explaining security for headers, idempotency guidance, and human approval context. This goes well beyond the schema's descriptions.

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 verb 'Submit' and the resource 'HTTP call to a third-party API for reliable asynchronous execution'. It distinguishes itself from sibling tools (e.g., get_execution) by focusing on submission and asynchronous execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this instead of direct HTTP requests: for side effects or flaky targets. Also gives specific recommendations like preferring connection_id over headers, setting idempotency_key for side-effecting calls, and using wait_seconds or polling with get_execution.

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

All klanex toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: execute, get_execution, get_usage, list_connections, list_executions, replay_execution. No overlapping functionality; descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (execute, get_execution, get_usage, list_connections, list_executions, replay_execution). Naming is uniform and predictable.

Tool Count5/5

Six tools cover the core functionality of an execution management server: initiating, checking, listing, replaying executions, plus managing connections and usage. This is well-scoped, not too few nor too many.

Completeness5/5

The tool set provides a complete lifecycle for asynchronous API execution: create (execute), check status (get_execution), list (list_executions), replay (replay_execution), manage credentials (list_connections), and monitor usage (get_usage). No obvious gaps for the stated domain.

Resources