Skip to main content
Glama

MORVS

by ai.morvs.api
OverviewDiscussionsAdmin

Compare Data Broker Registries

data_broker_diff
Read-onlyIdempotent

Compares two files of the MORVS California Data Broker Register (a yearly CPPA registry, named by its year, or the Attorney General's 2020-2023 list) under the register's published method: a registration in the earlier file whose normalised legal name has no registration in the later file is an apparent leaver; if its website domain does have a later registration it is counted as re-registered at the same domain, with the later names, otherwise as not re-registered under either name or domain; a later registration whose name and domain are both absent earlier is net new. Returns the counts and the named registrations in each group, plus the register's own published figures for consecutive files. A registration absent from a later file is not an exit, a merger or a finding: registration is self-reported and California-only, and a business may have stopped brokering, merged, changed domain or simply not filed.

Input Schema

NameRequiredDescriptionDefault
year_aYesOne register file the register carries: a CPPA registry year (YYYY, 2024 onward) or 2020-2023 (Attorney General list). Order does not matter.
year_bYesThe other register file, different from year_a: a CPPA registry year (YYYY) or 2020-2023. The earlier file is reported as earlier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / year_a / description
      Previous value: -"One register file: 2026, 2025 or 2024 (CPPA registry) or 2020-2023 (Attorney General list). Order does not matter."New value: +"One register file the register carries: a CPPA registry year (YYYY, 2024 onward) or 2020-2023 (Attorney General list). Order does not matter."
    • removedInput schema / properties / year_a / enum
      Removed value: -[
-  "2026",
-  "2025",
-  "2024",
-  "2020-2023"
-]
    • addedInput schema / properties / year_a / pattern
      Added value: +"^[0-9]{4}(?:-[0-9]{4})?$"
    • changedInput schema / properties / year_b / description
      Previous value: -"The other register file, different from year_a: 2026, 2025, 2024 or 2020-2023. The earlier file is reported as earlier."New value: +"The other register file, different from year_a: a CPPA registry year (YYYY) or 2020-2023. The earlier file is reported as earlier."
    • removedInput schema / properties / year_b / enum
      Removed value: -[
-  "2026",
-  "2025",
-  "2024",
-  "2020-2023"
-]
    • addedInput schema / properties / year_b / pattern
      Added value: +"^[0-9]{4}(?:-[0-9]{4})?$"
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/closed-world safety profile, and the description goes well beyond them: it explains the classing logic (apparent leaver, re-registered at same domain, net new) and, crucially, warns that an absent registration is NOT an exit, merger, or finding because registration is self-reported and California-only. That is exactly the kind of interpretive caveat an agent needs.

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?

Front-loaded with the verb and resource, and the method and caveats are packed efficiently. It is a dense single paragraph and slightly long, but nearly every clause (method, classing, caveat) carries information an agent uses.

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?

No output schema exists, and the description compensates by specifying what is returned (counts and named registrations per group, plus the register's own published figures for consecutive files). Combined with the interpretation caveats, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both year_a and year_b are already documented in the schema. The description reinforces the accepted formats ('named by its year, or the Attorney General's 2020-2023 list') but adds no syntax or ordering detail beyond what the schema provides, so the baseline 3 applies.

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 ('Compares two files of the MORVS California Data Broker Register') and pins down the exact domain (CPPA yearly registry or AG 2020-2023 list). An agent can separate this from the sibling data_broker_check 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 Guidelines3/5

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

The description implies usage by laying out the register's published comparison method and what the result means, but it never states when to reach for this tool over data_broker_check or other broker-related siblings, nor any exclusions. Usage is inferable from the resource described rather than being routed explicitly.

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

All MORVS toolsInspect
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