VHGENGINE

by app.railway.up.engine-production-3bdc

redrive_webhook_delivery

Requeue a dead-lettered webhook delivery: reset to pending, due now. Admin scope.

    Valid ONLY on a `dead` delivery (a live receiver that exhausted its retries); any other
    status is a 409 conflict and a delivery you do not own is not_found. It re-attempts
    through the normal pipeline and, if it dies again, dead-letters normally. Args:
    delivery_id (from list_webhook_deliveries), api_key. Returns the refreshed row. Errors:
    unauthorized, forbidden, not_found, conflict, rate_limited.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	API key for this call. Omit to fall back to the Authorization: Bearer / X-API-Key request header (streamable-HTTP only), then the VHGENGINE_API_KEY env var (the stdio default). No key resolvable -> unauthorized.
`delivery_id`	Yes	The delivery to requeue, from list_webhook_deliveries. Only a `dead` row can be redriven; any other status is a conflict and a delivery you do not own is not_found.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Last failure reason, or null.
`status`	No	Reset to 'pending' and due now.
`dead_at`	No	When it was dead-lettered, or null once redriven.
`attempts`	No	Attempts so far; the redrive adds to this count.
`created_at`	No	When the delivery was first enqueued, ISO-8601 UTC.
`event_type`	No	The event this delivery carries.
`delivery_id`	No	The delivery that was requeued.
`delivered_at`	No	When it finally succeeded, or null.
`next_attempt_at`	No	When the pipeline will try again, ISO-8601 UTC. Null on a terminal row.
`payload_preview`	No	First 200 chars of the body; the full body is never returned.
`last_status_code`	No	HTTP status of the most recent attempt, or null.

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries full burden. It discloses the state reset, admin scope, validity constraints, error responses, and the re-attempt/dead-letter behavior. This is thorough and adds significant context beyond the schema.

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?

The description is well-structured, front-loaded with the core purpose, and every sentence provides necessary detail. It efficiently uses a paragraph for constraints and a bullet-style list for errors, avoiding redundancy.

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 the presence of an output schema, the description doesn't need to detail return values, but it still covers all essential context: prerequisites, constraints, behavior, and errors. It is complete for a mutation tool with no annotations.

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 100%, so the schema already documents both parameters thoroughly. The description lists 'Args: delivery_id ... , api_key' but adds minimal new meaning beyond what the schema provides, though it does note the source of delivery_id and the auth fallback behavior for api_key already in 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?

The description clearly states the tool's purpose with a specific verb and resource: 'Requeue a dead-lettered webhook delivery: reset to pending, due now.' It also distinguishes from siblings by focusing on the redrive action for dead deliveries, which is unique.

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 explicit when-to-use and when-not-to-use conditions: 'Valid ONLY on a `dead` delivery' and specifies 409 conflict for other statuses. It also gives context about ownership and re-attempt behavior. However, it does not explicitly name alternative tools, though it references list_webhook_deliveries as the source for delivery_id.

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

All VHGENGINE tools Inspect

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.1/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, e.g., signup vs. delete_account, create_key vs. revoke_key, generate_hooks vs. score_hook. Even similar tools like generate_hooks and generate_hooks_batch are clearly differentiated by single vs. batch operation.

Naming Consistency5/5

All 32 tools use a consistent verb_noun snake_case pattern (e.g., add_credits, create_checkout, revoke_key, list_outcomes) with no mixing of camelCase or other conventions.

Tool Count4/5

32 tools is slightly above the typical 15-tool range, but the domain is broad (account, keys, webhooks, generation, scoring, jobs, outcomes), and each tool has a specific purpose. No tools seem redundant.

Completeness4/5

The tool surface covers most lifecycle operations: CRUD for accounts/keys/webhooks, generation/scoring with batch and async variants, outcomes reporting, and auxiliary tools. Missing explicit delete for hooks (expire automatically) and some update operations, but no critical gaps.

Resources

Need Help?