vicp-registry

search_cases

Search VICP cases with structured filters.

- query: free text matched against petitioner identifier, condition,
  package id, caption name and the AI case summary.
- vaccine: canonical vaccine name (use get_filters() for valid values,
  e.g. "Influenza (flu)", "DTaP/DPT", "MMR", "COVID-19", "Hepatitis B").
- condition_category / outcome: exact values from get_filters().
- decision_type: how the case was decided (stipulation, proffer,
  reasoned, reasoned_damages, procedural, unclear).
- pediatric_only uses the broad pediatric cohort definition
  (is_minor OR is_minor_inferred OR age<18) â€” strict age-only filtering
  undercounts pediatric cases substantially.
- dates are ISO strings (YYYY-MM-DD); awards are USD integers.
- sort: decision_date_desc|decision_date_asc|filed_asc|filed_desc|award_desc|award_asc
- Returns total match count plus one page of compact case records with
  canonical URLs. Use get_case(package_id) for the full record.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	decision_date_desc
`limit`	No
`query`	No
`offset`	No
`outcome`	No
`vaccine`	No
`attorney`	No
`filed_to`	No
`is_death`	No
`max_award`	No
`min_award`	No
`decided_to`	No
`filed_from`	No
`decided_from`	No
`decision_type`	No
`autism_related`	No
`pediatric_only`	No
`special_master`	No
`condition_category`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 16, 2026

addedInput schema / properties / decision_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Decision Type"
+}

First observedJul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Despite no annotations, the description discloses important behavioral traits: returns compact records with canonical URLs, paginates via limit/offset, uses ISO date strings and integer awards, and explains the pediatric_only definition. It does not mention rate limits or authentication, but the core behavior is well-covered.

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?

The description is well-structured with bullet points and front-loaded information. Each sentence adds value, though the description is slightly long. It efficiently conveys necessary details without tautology.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 19 parameters, no annotations, and no output schema, the description provides a good overview but lacks detail on some parameters and on the exact structure of return records (e.g., fields in compact records). It directs to get_case for full records but does not fully describe the output format, leaving some information missing.

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 description coverage is 0%, so the description must explain parameters. It covers query, vaccine, condition_category, outcome, decision_type, pediatric_only, date range, award range, and sort options. However, it omits several parameters (attorney, is_death, autism_related, special_master, limit, offset) or provides only minimal context, leaving gaps for those fields.

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 states 'Search VICP cases with structured filters' and lists specific searchable fields (query, vaccine, condition_category, etc.). It distinguishes from siblings by referencing get_filters for valid values and get_case for full records, making the tool's 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 guidance on using get_filters for valid values and get_case for full records, which helps distinguish from related tools. However, it does not explicitly compare to sibling tools like 'search' or 'search_attorneys', leaving some ambiguity about when to use this specific tool versus alternatives.

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

All vicp-registry 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?