Verify a Florida business in official Sunbiz records: status, agent, officers. 0.10 USDC via x402.
Scored across 1 tool
With a single, narrowly scoped tool there is no possibility of misselection between tools. The tool's purpose (verify a Florida business by name against Sunbiz-derived records) is unambiguous and clearly stated.
The sole tool follows a clear verb_noun pattern (verify_florida_business), snake_case, and the verb matches the action described. No competing conventions exist to create inconsistency.
A one-tool surface is borderline thin: the free preview and the paid full lookup are fused into a single call, so there is no separate lightweight 'preview' or 'fetch by id' operation. For a lookup-only service this is defensible, but the surface feels sparse.
Name-based verification, preview, and full paid detail (status, agent, officers, filings, history) cover the core domain well. Minor gaps exist: no lookup by document number, no officer/registered-agent search, and no batch verification, which agents must work around via name lookups.
Looks up a company by name in Florida Division of Corporations public records (the records behind Sunbiz). This tool is free: it checks the name, reports the date of the newest Florida file we hold, lists the legal names of up to 3 candidate filings while the hourly free preview lasts, and returns the pay URL for the full lookup. The full lookup (document number, status as reported, filing type, filing date, principal city, registered agent, officers, home state, annual report status, status history and source file) costs 0.10 USDC per lookup over x402 v2 on Base, charged even when nothing matches. Paid answers carry warning flags, each with the Florida record behind it. The buyer's own x402 wallet pays at the pay URL; this server never receives payment, signatures or keys. A no match result is not proof that a company does not exist. Florida only. Not affiliated with the Florida Department of State.
| Name | Required | Description | Default |
|---|---|---|---|
| home_state | No | Optional two letter US state code where the company was formed, such as DE. The paid lookup lists filings from that state first. | |
| max_results | No | How many candidate filings the paid lookup returns, 1 to 5. Default 5. | |
| business_name | Yes | The company name to look up, such as Publix Super Markets. 2 to 200 characters. |
| Name | Required | Description |
|---|---|---|
| query | Yes | |
| dataset | Yes | |
| payment | Yes | |
| preview | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only cover the read-only/idempotent/closed-world safety profile; the description adds what an agent actually needs: the free preview contents (up to 3 candidate legal names, newest Florida file date), the exact paid field list, per-lookup pricing over x402 v2 on Base, that payment is charged on a miss, that payment flows through the buyer's own wallet and the server never touches keys, and the no-match-is-not-proof caveat. That is substantial disclosure beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and free behavior before the pricing and legal disclaimers, and the disclosure sentences each carry real decision-relevant information. It runs long and stacks several caveats (x402 mechanics, non-affiliation, no-match disclaimer) that could be tightened, but nothing is filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not describe return values in depth, and it does not need to. It nevertheless covers the economics, preview limits, jurisdiction, payment mechanics, and interpretation caveats of a fairly complex paid lookup — everything an agent needs to call it correctly and read the result honestly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so every parameter is already documented in the input schema and the baseline is 3. The description adds only indirect meaning — the free preview returns up to 3 candidates while the paid lookup returns more — and never mentions home_state's ordering effect or restates max_results semantics, so it does not go meaningfully beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Looks up a company by name in Florida Division of Corporations public records" gives a specific verb (looks up) and resource (company name), plus the jurisdiction (Florida only) and the data source (Sunbiz). The free-vs-paid split of what each tier returns is stated explicitly, so an agent knows exactly what it is invoking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is clear: Florida-only scope, a free preview that runs only "while the hourly free preview lasts," and the fact that the full lookup costs 0.10 USDC "charged even when nothing matches." There are no siblings to route between, so the absence of an explicit alternative is fine, but the description does not say when a caller should skip the paid step entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
verify_florida_businessFlorida Sunbiz corporation, LLC and non-profit search with officer and registered agent lookup.
Search Florida business filings. Needs an LLCDrop key (Starter, Agency or Enterprise plan).
Verify a US business exists and is active by name + state. Status, formation date, agent.
Confirm a US business is real and find who controls it. 32.6M official registry records.
Add one secure layer between your agents and this server.