Revalidata: Contract Deadlines and Critical Dates

Account and credits

prism_get_account

Read-only

Returns this Revalidata account's credits and prices: credits remaining, the price per contract ($0.50), whether an Unlimited subscription covers everything, and how many contracts were added this month. creditStatus is unlimited, ok, low (2 or fewer left) or empty -- check it before a batch and, when it is low or empty, ask your user before calling prism_buy_credits. purchaseOptions.checkoutLink says whether that returns a checkout link for your user to pay.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prism_get_account"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`pricing`	Yes
`nextStep`	Yes	What the agent should do next, in plain words; null when nothing is needed. A step that would spend credits or money says to ask your user first: do not take it on your own.
`creditStatus`	Yes	Where the account's credits stand: unlimited (subscription), ok, low (2 or fewer left), or empty (none; unlocking a preview that withholds facts returns code insufficient_credits).
`purchaseOptions`	Yes	Which ways of buying credits are available right now.
`creditsRemaining`	Yes
`lowCreditThreshold`	Yes	creditStatus is low at this many credits or fewer.
`monthlyContractLimit`	Yes
`unlimitedSubscription`	Yes	Whether an Unlimited subscription covers every contract.
`contractsAddedThisMonth`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral context by defining the creditStatus thresholds (low = 2 or fewer left) and explaining what purchaseOptions.checkoutLink implies for the user's payment step. The one weakness is that much of the sentence is a field-by-field restatement of the response, which the output schema already supplies.

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?

Two sentences, front-loaded with the return content and followed by the actionable rule, so the most decision-relevant line is easy to find. Minor waste comes from listing individual return fields that the output schema already documents.

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 zero-parameter read tool with an output schema, the description supplies everything an agent needs: what it returns, how to interpret creditStatus, and what to do next when credits run out. Nothing required for correct invocation is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The prose correctly implies a no-argument call, and no parameter claims are made that could mislead.

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?

Opens with a specific verb and resource ("Returns this Revalidata account's credits and prices") and then enumerates the concrete contents: credits remaining, price per contract, Unlimited coverage, contracts added this month. An agent can distinguish this from prism_buy_credits or prism_list_contracts without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit call site ("check it before a batch") and an explicit escalation rule ("when it is low or empty, ask your user before calling prism_buy_credits"). It names the alternative tool and the exact condition that should route the agent to it.

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.