MCC Solutions

Online notarization (RON) with a New Jersey notary

online_notarization_info

Read-onlyIdempotent

Price, hours, legal basis and booking link for a remote online notarization session with a New Jersey notary; signers can be anywhere in the U.S.

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": "online_notarization_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`service`	Yes
`signers`	No
`book_url`	Yes
`price_usd`	No
`disclaimer`	No
`legal_basis`	No
`acceptance_check`	No
`extra_signer_usd`	No
`not_available_for`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world lookup, so the description is not obligated to restate safety. What it does add is genuinely useful behavioral context the annotations cannot: the jurisdictional constraint (New Jersey notary) and the eligibility scope (signers may be located anywhere in the U.S.), which affects whether the tool is even applicable to a user's situation.

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?

A single semicolon-joined sentence that front-loads the concrete deliverables (price, hours, legal basis, booking link) before the qualifying scope clause. There is no filler, hedging, or repetition of the title.

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?

With zero parameters and an output schema present, the description only needs to convey what the tool is for and who it applies to, and it does both. The enumerated items map cleanly onto expected return contents. It could note whether eligibility requirements or document types are also returned, but nothing essential to 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 the schema carries no semantics to explain and the baseline of 4 applies. The description correctly implies the tool is parameterless by framing the call as a fixed informational lookup for one service rather than a query the agent must shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (remote online notarization with a New Jersey notary) and enumerates the payload an agent will receive: price, hours, legal basis and booking link. That is far more concrete than the tool name alone. It stops short of explicitly distinguishing itself from data-oriented siblings such as get_services_and_prices, so it is clear but not sibling-differentiated.

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

Usage Guidelines3/5

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

Usage is implied: this is the lookup to run when a user asks about RON cost, availability or legality, and the mention of a booking link hints at a downstream booking flow. However, there is no explicit 'use this when...' statement and no exclusion pointing an agent to request_service or get_services_and_prices for the actual booking or catalog step. An agent can infer the context but is not routed.

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

All MCC Solutions 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.

Resources

Need Help?