venumark

get_scorecard

One vendor's public compliance record: letter grade (or withheld when the current DBPR license cannot be confirmed), license status, inspection recency, and record shape. Look up by vendor_id from search_vendors, or directly by license_number (MFD3953067 or 3953067) to vet a vendor in one call. Grades: A to F, plus HOLD (active DBPR license hold), Ungraded (insufficient record), and Withheld (license unconfirmed).

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

Input Schema

Name	Required	Description	Default
`vendor_id`	No	Vendor id (UUID) from search_vendors
`license_number`	No	Florida DBPR license number, with or without the letter prefix

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses that the tool reads public compliance records and explains grade values (including HOLD, Ungraded, Withheld). However, it does not mention caching, staleness, rate limits, or any destructive behavior, which is acceptable for a read-only tool but could be more comprehensive.

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?

The description is a single, dense paragraph that front-loads the core purpose ('One vendor's public compliance record') and every sentence adds value. No extraneous information, achieving high informational density without waste.

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?

Given no output schema and no annotations, the description covers key output fields (grade, license status, inspection recency, record shape) and explains the grading scale. It is complete enough for a straightforward read operation, though it could mention the response format or any pagination limits.

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?

Schema coverage is 100% with descriptive parameter fields. The description adds context by specifying that vendor_id comes from search_vendors and providing license_number format examples (MFD3953067 or 3953067), enhancing clarity beyond the schema alone.

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?

The description clearly identifies the tool as retrieving a vendor's public compliance record, listing specific fields (letter grade, license status, inspection recency, record shape). It distinguishes from sibling tools like search_vendors, which returns vendor IDs, making the purpose unambiguous.

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?

The description provides clear lookup instructions (by vendor_id from search_vendors or directly by license_number) and explains grade meanings. However, it does not explicitly state when not to use this tool or compare it to alternatives like decide_vendor, leaving some ambiguity.

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?