Loading ToolBench
California state contract awards & purchase orders: search, top vendors, agency spend — keyless
Five tools with complete, well-structured schemas and detailed descriptions. All tools have proper input schemas with typed parameters and descriptions. Tool names follow verb_noun pattern (search_, aggregate, rank, profile). Descriptions are comprehensive (150 - 250 chars), explaining WHAT, WHEN, and context. Parameters include enums (sort), ranges (limit 1 - 100), and clear constraints. No output schemas documented. Error handling not visible in source. All tools are read-only (no destructive operations), reducing risk. Missing: output schema documentation, error recovery guidance, and parameter validation rules in descriptions.
Search California STATE government contract awards & purchase orders from the official State Contract and Procurement Registration System (SCPRS) on data.ca.gov. Each result is a State purchase order / award with its awarding department (agency), the winning supplier (vendor), the dollar amount, acquisition type/method, item description, and dates. Filter by supplier, department/agency, keyword, fiscal year, acquisition type, and/or a minimum amount; results are ranked by dollar amount (biggest awards first) by default. Use this for questions like "who won California state contracts", "biggest suppliers to the CA Department of Health Care Services", or "CA state purchase orders for laptops". This is CALIFORNIA STATE data (not federal).
Rank what the State of California spends the most on, by commodity category (UNSPSC commodity title), from the SCPRS purchase-order data on data.ca.gov. Returns each category with total dollars and purchase-order count, largest first, optionally scoped to a department/agency or fiscal year. Answers "what does California buy the most of", "top spending categories for the CA Department of Health Care Services". This is CALIFORNIA STATE data (not federal).
Profile a California STATE department/agency's procurement spend from the SCPRS purchase-order data on data.ca.gov: total dollars, purchase-order count, top suppliers (vendors) it buys from, top commodity categories it spends on, and a by-fiscal-year breakdown. Matches the department name as a case-insensitive substring. Answers "what does the CA Department of Justice buy and from whom", "which agencies spend the most". This is CALIFORNIA STATE data (not federal).
Output schemas not documented. LLMs cannot predict response structure, field names, or types. Downstream tool chaining and result extraction become error-prone.
No error handling or recovery guidance in tool descriptions. If a query returns no results or the API fails, LLMs have no guidance on what to do next.
Parameter descriptions include example values (e.g., 'e.g. "Microsoft", "Pitney Bowes"'). LLMs tend to reuse examples literally rather than adapting to context, causing false positives.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Aggregate a supplier's California STATE contract awards from the SCPRS purchase-order data on data.ca.gov: total dollars awarded, number of purchase orders, and a breakdown by awarding department (agency) and by fiscal year. Matches the supplier name as a case-insensitive substring, so it also surfaces name variants (e.g. "Pitney Bowes" vs "Pitney Bowes, Inc"). Use this to size up a single vendor's business with the State of California. This is CALIFORNIA STATE data (not federal).
Rank the biggest suppliers (vendors) to the State of California by total contract/purchase-order dollars, from the SCPRS purchase-order data on data.ca.gov. Answers "who are California's largest state contractors / award winners", optionally scoped to a department/agency, a fiscal year, an acquisition type, or an item keyword. Returns each supplier with total dollars awarded and purchase-order count, largest first. This is CALIFORNIA STATE data (not federal).
No pagination guidance in descriptions. Tools accept limit/offset but descriptions don't explain default behavior, max results, or when pagination is needed.
No tool annotations (readOnlyHint, idempotentHint). While all tools are read-only, explicit annotations would help MCP clients optimize caching and retry logic.