Revalidata: Contract Deadlines and Critical Dates

Get a link to buy credits

prism_buy_credits

Returns a Stripe checkout link for your user to buy credits ($0.50 each, 20-2000 at a time). This tool cannot pay: it only returns the link, and your user opens it and pays on the Stripe page themselves. Ask your user before calling it. Credits are added as soon as their payment completes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "credits": "<credits>"
    },
    "name": "prism_buy_credits"
  }
}

Input Schema

Name	Required	Description	Default
`credits`	Yes	How many credits, 20 or more.

Output Schema

Name	Required	Description
`amount`	Yes	Total price, e.g. $10.00.
`credits`	Yes
`nextStep`	Yes
`checkoutUrl`	Yes	Stripe checkout link to give the user; they pay on it themselves.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare non-read-only, open-world, non-idempotent behavior; the description supplies the crucial human-in-the-loop detail — the agent never pays, the user opens the Stripe page, and credits land only after payment completes. It stops short of saying whether repeated calls spawn additional checkout sessions, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with the return value, followed by the constraint and the timing of credit delivery. No filler or repetition of the title.

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 one-parameter tool with an output schema, the description covers everything an agent needs: what is returned, that the agent cannot complete payment, the consent requirement, and when credits become available.

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 single parameter is fully documented, so the baseline is 3. The description still adds real meaning beyond the schema by attaching a price ($0.50 each) to the credits argument, letting the agent reason about cost before calling.

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?

States a specific verb and resource ('Returns a Stripe checkout link ... to buy credits') along with scope details (price per credit, 20-2000 range). An agent can instantly tell this is a payment-link generator rather than an account or contract operation like its siblings.

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?

Gives a clear precondition ('Ask your user before calling it') and explicitly rules out a wrong expectation ('This tool cannot pay: it only returns the link'). It does not name alternative tools, but no sibling performs purchasing, so the guidance covers the realistic decision point.

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

All Revalidata: Contract Deadlines and Critical Dates 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.