Skip to main content
Glama
Sign In

Crosodo

by com.crosodo
OverviewDiscussionsAdmin

Lookup county cottage-food requirements

lookup_county
Read-onlyIdempotent

County-level cottage-food requirements for a US state + county from Crosodo's structured county dataset (contacts, verification status, local URLs, state summaries). Unknown states or counties return an error — never invented data. Cottage food laws change. This summary is generated from Crosodo's hand-maintained dataset — it is not legal advice. Verify with your county before selling.

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": {
      "state": "<state>",
      "county": "<county>"
    },
    "name": "lookup_county"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes2-letter USPS abbrev (PA) or state slug (pennsylvania)
countyYesCounty name or slug (lancaster or Lancaster County)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: unknown states/counties return an error rather than fabricated data, results come from a hand-maintained dataset, and content is not legal advice. Read-only/idempotent is already covered by annotations, so these additions are the value. Missing only return-shape detail (fields listed in parenthetical, no pagination/freshness caveat on staleness).

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 purpose followed by the error-behavior guarantee and a legal disclaimer; every sentence carries information. Slight redundancy between 'never invented data' and the 'hand-maintained dataset' line, and the disclaimer block is a bit long for the payload.

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?

A two-param read-only lookup with full schema coverage and no output schema is well served: scope, failure mode, data provenance, and legal caveat are all present. Lacking only minor detail on what the returned summary contains and how current it is, which the parenthetical only partially covers.

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 both parameters already document accepted formats (2-letter abbrev or slug; 'lancaster' or 'Lancaster County'), so the baseline of 3 applies. The description adds no format or normalization guidance 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?

Specific verb (lookup) + resource (county-level cottage-food requirements) + the exact key space (US state + county), and it names the underlying dataset. The agent can distinguish this from lookup_state_law (state-level) without opening either 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?

Usage is implied by the name and by the contrast with the state-level sibling, but no explicit 'use this instead of lookup_state_law when you need county-specific rules' routing is stated. The 'verify with your county before selling' line gestures at when the result matters but is not a selection guideline.

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

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