VHGENGINE

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

create_key

Mint a new named API key; the plaintext is returned ONCE. Requires admin scope.

    Delegate safely (WP-SCOPE): optional scopes (subset of read|spend|admin; omit for
    full power) + daily_credit_cap (credits/day; omit for uncapped) hand a sub-agent a
    key that can only do what you allow. Args: name (1-100), api_key (an admin-scoped
    key). Returns {api_key (store it), prefix, name, scopes, daily_credit_cap,
    created_at}. Errors: unauthorized, forbidden, invalid_request, rate_limited.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Label for the new key, 1-100 chars, shown by list_keys so you can tell delegated keys apart. Defaults to 'key'.	key
`scopes`	No	Powers the new key gets: read (free reads), spend (charged generate/score/remix), admin (key + account + webhook management). OMIT for a full-power key; pass a subset to hand a sub-agent strictly less power than you hold.
`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.
`daily_credit_cap`	No	Credits this key may spend per UTC day, 1-100000; further charges on it are refused once reached (other keys are unaffected). Omit for uncapped. list_keys reports spent_today against this.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	The label you gave it.
`prefix`	No	First 12 chars, used by list_keys / revoke_key / get_usage(key_prefix=...).
`scopes`	No	Powers granted, a subset of read/spend/admin (all three = full power).
`api_key`	No	The plaintext key. Store it now; it is never readable again.
`created_at`	No	Creation time, ISO-8601 UTC.
`daily_credit_cap`	No	Per-UTC-day spend ceiling, or null for uncapped.

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full burden. It discloses the one-time plaintext return, admin scope requirement, full-power vs scoped behavior, daily cap semantics, auth parameter, return fields, and error types. This is rich, honest behavioral disclosure.

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 structured into a quick-essential first line, a delegation rationale paragraph, then compact Args/Returns/Errors lines. Every sentence adds value—no fluff or repetition—and it stays focused despite covering critical security details.

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?

The tool has 4 params, an output schema, and genuine complexity (auth scopes, caps, one-time secret). The description covers purpose, usage, return shape, auth requirements, and error cases. It is complete enough to invoke correctly without external documentation.

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% and the schema descriptions are already strong, but the description adds clarifying meaning: 'omit for full power,' 'store it' for the returned api_key, and 'admin-scoped key' for the api_key parameter. This goes beyond the schema baseline.

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 opens with 'Mint a new named API key; the plaintext is returned ONCE. Requires admin scope,' which uses a specific verb ('mint'), resource ('API key'), and key trait (one-time plaintext). This clearly distinguishes it from siblings like list_keys, revoke_key, and add_credits.

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 explicitly states the admin-scope requirement and positions delegation use cases: 'Delegate safely... hand a sub-agent a key that can only do what you allow.' It does not name alternative tools, but the purpose is clearly distinct from revoke_key or list_keys, and the context is sufficient.

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?