MCC Solutions

Open notary appointment times

available_times

Read-onlyIdempotent

Open appointment times for online notarization (ron, by video, signer anywhere in the U.S.) or a mobile notary visit in New Jersey (mobile) over the next days (up to 14), in Eastern Time. Returns a per-day summary (days: open count, first and last time, how many after 3 PM) and every open slot a page at a time (slots, with limit, offset, has_more and next_offset), plus the booking link. Morning and daytime times are included; the most openings are after 3 PM and in the evening. To book, send up to 3 slot start values to request_service (service "ron" or "mobile_notary_nj") in start_times, or open the booking link.

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

Input Schema

Name	Required	Description
`days`	No	How many days to look ahead (default 7)
`from`	No	Start date YYYY-MM-DD (default today, Eastern)
`part`	No	Only times after 3 PM, or only before 3 PM
`limit`	No	Slots per page (default 30)
`offset`	No	Skip this many slots (use next_offset from the last page)
`service`	No	ron = online by video; mobile = we travel to the signer in NJ

Output Schema

Name	Required	Description	Default
`days`	Yes
`note`	No
`part`	No
`limit`	No
`slots`	Yes
`offset`	No
`service`	Yes
`book_url`	Yes
`has_more`	No
`matching`	No
`returned`	No
`timezone`	Yes
`total_open`	Yes
`how_to_book`	No
`next_offset`	No
`morning_midday_times`	No
`afternoon_evening_times`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description goes well beyond that, disclosing the return shape (per-day summary with open count, first/last time, count after 3 PM, plus paginated slots, has_more and next_offset), the booking link, the timezone, and the 14-day cap — behavior an agent needs before calling.

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?

It is a single front-loaded paragraph that leads with what the tool does, then return shape, then next-step routing — no filler. It is dense and slightly long, but nearly every clause carries information an agent would otherwise have to infer.

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 read-only availability tool with an output schema, all six optional parameters documented at 100% coverage and full annotations, the description supplies everything extra an agent needs: timezone, lookahead cap, pagination flow, the ron/mobile service mapping, and the handoff path to request_service.

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%, so the baseline is 3, but the description adds real meaning on top: it explains the 14-day ceiling in prose, notes that morning and daytime times are included and that most openings are after 3 PM, which gives the 'part' enum operational significance. Pagination semantics (limit, offset, next_offset) are also restated, though without extra depth beyond the schema.

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 states a specific verb and resource — fetching open appointment times for online notarization (ron) or a mobile notary visit in New Jersey (mobile) over the next up-to-14 days in Eastern Time. It explicitly names the two service modes and the time window, so an agent can tell exactly what this tool returns without opening the 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?

It gives explicit routing: this tool is for discovering availability, and 'To book, send up to 3 slot start values to request_service (service "ron" or "mobile_notary_nj") in start_times, or open the booking link' names the alternative tool and the condition that selects it. The ron vs mobile distinction also tells the agent which service value to carry forward.

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?