MCC Solutions

List MCC state-rule datasets

list_datasets

Read-onlyIdempotent

List the 27 state-by-state legal and employer datasets (final pay, minimum wage, meal breaks, security deposits, small claims, small estates, apostille offices and more) with versions, check dates and record counts. Free; records need an MCC Data API key (plans from $19/month).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context the annotations cannot: the call is free, but consuming records requires an MCC Data API key with paid plans from $19/month. It does not cover pagination or response shape, but with zero params and a fixed catalog that matters little.

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?

A single front-loaded sentence that leads with the verb and the catalog scope before the metadata and pricing. Slightly dense with the parenthetical list and the price detail, but every clause carries signal for an agent deciding whether to call it.

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 no parameters and no output schema, the description must convey what comes back, and it does (datasets with versions, check dates, record counts). The one gap is the explicit handoff to the record-fetching sibling and any key/auth mechanics beyond the price mention, which an agent would have to infer.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not need to explain inputs, and it correctly spends its words on the output contents instead.

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 (List) and a precisely scoped resource: 27 state-by-state legal/employer datasets, with parenthetical enumeration of the domain areas (final pay, minimum wage, meal breaks, security deposits, small claims, small estates, apostille offices). Also names the metadata returned (versions, check dates, record counts), which separates it from get_dataset_records at a glance.

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?

Implies the browse-then-fetch flow by noting the listing is free while records need an API key, and the sibling get_dataset_records is the obvious next step, but the description never explicitly says when to use this vs get_dataset_records or list_free_tools, nor states the prerequisite ordering overtly. Usage is inferable rather than stated.

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?