Skip to main content
Glama
Sign In

LLCDrop

by com.llcdrop
OverviewDiscussionsAdmin

List parcels owned by a business

list_business_parcels
Read-onlyIdempotent

Parcels owned by one business (a Sunbiz entity), highest value first, at most 50. Each parcel counts as one row.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "list_business_parcels"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id returned by the list endpoints, a positive integer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the description adds the non-obvious operational traits: results are ordered highest value first and hard-capped at 50. The one-row-per-parcel note tells the agent the result is flat, not nested. It doesn't mention what happens when a business owns more than 50 parcels beyond the cap.

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?

Two short sentences, front-loaded with what is returned, then the sort order, cap, and row granularity. No filler and nothing repeated from annotations or schema.

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 one simple parameter and no output schema, the description gives the essentials an agent needs: unit of return (one row per parcel), ordering, and a size limit. It stops short of indicating anything about fields per parcel or pagination beyond the 50 cap.

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% and the sole parameter is documented, so the baseline is 3. The description adds only a light hint that the id refers to a business entity rather than a parcel, which partially clarifies an ambiguity in the schema wording ('id returned by the list endpoints').

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?

States a specific verb and resource ('Parcels owned by one business') and adds scope qualifiers (one Sunbiz entity, top 50 by value). It implicitly separates itself from search_parcels via the single-business scoping, but never names that sibling explicitly.

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 only implied: 'owned by one business' suggests the id must be a business entity and that broad cross-business lookups belong elsewhere. There is no explicit when-to-use or when-not-to-use statement, and no named alternative such as search_parcels or get_parcel.

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

All LLCDrop 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