VHGENGINE

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

get_creator_profile

Read-only

Get the current or one exact historical creator-profile version. Read scope.

    Foreign, deleted, and unknown ids all return the same not_found envelope. Returns
    the same profile object as REST. Errors: unauthorized, forbidden, not_found,
    invalid_request, rate_limited.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`version`	No	Exact immutable version; omit for the current version.
`profile_id`	Yes	Account-owned creator profile id returned by create/list profiles.

Output Schema

TableJSON Schema

Name	Required	Description
`stance`	No	Caller-declared speaker stance.
`creator`	No	Caller-declared creator description.
`version`	No	Exact immutable version returned by this read or write.
`audience`	No	Caller-declared audience.
`created_at`	No	Profile creation time, ISO-8601 UTC.
`is_current`	No	Whether this immutable version is current.
`profile_id`	No	Opaque account-owned profile id.
`updated_at`	No	Current profile update time, ISO-8601 UTC.
`display_name`	No	Account-local profile label.
`secondary_use`	No	Three independent deny-by-default decisions.
`current_version`	No	Profile's current version.
`attestation_note`	No	Unverified-authority and non-consumption warning.
`consent_receipts`	No	Latest revision receipt for every decision.
`authority_attested`	No	The caller recorded the required authority attestation.
`first_person_facts`	No	Sanctioned caller-declared facts.
`rights_notice_text`	No	Exact immutable caller-authority notice text.
`version_created_at`	No	This version's creation time, ISO-8601 UTC.
`consent_notice_text`	No	Exact deny-by-default secondary-use notice text.
`subject_relationship`	No	Caller's declared relationship to the creator.
`rights_notice_version`	No	Immutable rights-attestation notice version.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, but the description adds valuable behavioral context: uniform not_found envelope for foreign/deleted/unknown IDs, return consistency with REST, and a specific error list. This exceeds annotation coverage and provides useful operational expectations.

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?

The description is concise and front-loaded with the core purpose. The additional sentences about error envelopes and REST parity are useful, though the error list could be considered slightly verbose for a description. Overall, it earns its place.

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?

For a simple read-only tool with full schema descriptions, an output schema, and a read-only annotation, the description is comprehensive: it covers purpose, version selection, edge-case behavior, error types, and return consistency. The context is complete enough for an agent to select and invoke the tool correctly.

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?

Since the input schema has 100% parameter description coverage, the description adds little beyond the schema. It echoes the version behavior ('current or one exact historical') but does not meaningfully enhance parameter understanding. Baseline 3 applies.

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: 'Get the current or one exact historical creator-profile version.' It uses a specific verb (Get) and resource (creator-profile version), and the scope ('current or one exact historical') differentiates it from sibling list/create/delete/update profile tools.

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 implies usage by focusing on a single profile version with an optional version parameter, which distinguishes it from listing all profiles. However, it does not explicitly mention alternatives like 'use list_creator_profiles to list all profiles', so it falls short of full usage guidance.

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?