MolTrust MCP Server

mt_travel_verify

Verify a travel booking against a TravelAgentCredential.

Runs a 10-step verification pipeline: VC signature, expiry, agent DID match,
segment authorization, spend limit, currency, daily cap, trust score,
delegation chain, and traveler binding.

Args:
    agent_did: DID of the booking agent (e.g. "did:base:0x...")
    vc_json: The TravelAgentCredential as a JSON string
    merchant: Merchant domain (e.g. "hilton.com")
    segment: Booking segment: hotel, flight, car_rental, or rail
    amount: Booking amount
    currency: Currency code (e.g. "USDC")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`amount`	Yes
`segment`	Yes
`vc_json`	Yes
`currency`	Yes
`merchant`	Yes
`agent_did`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the exact 10-step pipeline (signature, expiry, DID match, etc.), which is rich behavioral detail. It does not explicitly state read-only status or side effects, but the verification nature implies safety. The pipeline description adds significant value beyond a generic 'verify'.

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 structured with a summary line, a pipeline list, and an Args block. The pipeline list is slightly verbose but each item adds behavioral context. It is front-loaded with the purpose. A minor trim could be made, but it remains efficient.

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?

The description covers purpose, steps, and all parameters. It does not describe return values, but an output schema exists, which is acceptable. For a 6-param verification tool with no annotations, this is nearly complete. Missing explicit side-effect disclosure is a minor gap.

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?

Schema description coverage is 0%, so the description must compensate. It does so thoroughly: every one of the 6 parameters is described with context and examples (e.g., agent_did format, segment enum values, currency code). This is exactly what an agent needs to correctly populate arguments.

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 a precise verb-resource pair: 'Verify a travel booking against a TravelAgentCredential.' It further lists the 10-step verification pipeline, which clearly distinguishes it from sibling verify tools like mt_shopping_verify or mt_skill_verify. The scope is unambiguous.

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 clear context by stating it verifies travel bookings and names the credential type. However, it does not explicitly contrast with other verify tools or state when NOT to use it. Since there are many verify siblings, an explicit routing note would improve the score.

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

All MolTrust MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.