venumark

search_vendors

Search all licensed Florida food trucks and caterers (19,000+, scored from official DBPR inspection records). Matches business name, prior names, license number (MFD3953067 and 3953067 both work), and city. Optional county, grade, and limit filters. Grades: A to F, plus HOLD (active DBPR license hold), Ungraded (insufficient record), and Withheld (license unconfirmed). Returns matches with license status, letter grade, and a scorecard link.

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

Input Schema

Name	Required	Description
`city`	No	Optional Florida city filter, e.g. TAMPA
`grade`	No	Optional: only vendors currently holding this grade
`limit`	No	Max results, 1 to 25 (default 10)
`query`	No	Business name or license number (partial ok). Optional when city is given.
`county`	No	Optional Florida county filter, e.g. Hillsborough

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided; description adds context about data source (DBPR records) and return fields (status, grade, scorecard link), but does not disclose safety profile, authentication needs, or rate limits.

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 sentences, front-loaded with purpose, every sentence adds necessary detail without redundancy.

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, but description sufficiently explains return values (status, grade, scorecard link) and all parameters, making the tool self-contained for an agent.

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?

Adds value beyond 100% schema coverage by explaining license number format matching and elaborating on grade enum values (HOLD, Ungraded, Withheld).

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?

Clearly states 'Search all licensed Florida food trucks and caterers' with specific detail on searchable fields (name, license number, city) and distinguishes from sibling tools like get_scorecard.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Describes optional filters (county, grade, limit) and matching behavior, but does not explicitly contrast with alternative tools or state when not to use.

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

All venumark 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?