Skip to main content
Glama
mambalabsdev

Expert Witness Directory MCP Server

Find Expert Witnesses in the US and Australia

find_expert_witnesses
Read-only

Search deduplicated expert witness and medico-legal assessor records from US and Australian directories. Filter by specialty, region, country, and source to find the right professional.

Instructions

Find expert witnesses and medico-legal assessors in the United States and Australia. Reads 18 public directories (7 in the US, 11 in Australia, ABIME counted once), merges the same person across directories into one record, and maps every source's specialty tags to one taxonomy. Each row carries name, specialty, state or region, country, firm, practice site, phone, listing URL, and the sources that list the person. country accepts US and AU only: the public actor covers the United States and Australia and refuses a UK or Canadian request, so the run stops with an error on any other value. published_email is filled only when a source page printed an address; the actor never guesses an email. Several sources publish terms that restrict automated collection, reproduction, commercial use, or solicitation; the actor README lists each source's terms posture, and the use decision is yours. mode list returns every matching expert; mode feed returns only experts new, changed, returned, or removed since the last run on the same persistent store. Charges $0.004 per expert record, $0.01 per row with a published email, $0.002 per US row checked against NPPES when verifyNppes is on, and $0.00005 per actor start per GB of memory (one event at the 1024 MB default). Requires an APIFY_TOKEN and consumes Apify credits. Read only against the directories; it writes only to the named key-value store in your own Apify account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNolist returns every matching expert. feed returns only experts that are new, changed, or returned since the last run on the same persistent store, plus removed rows; unchanged experts are not emitted and cost nothing. A listing counts as removed after 2 complete, unfiltered runs miss it. Default: list.
regionNoState or region as the source prints it, for example Queensland, California, New South Wales. Case and accents are ignored. Empty returns every region.
countryNoUS, AU, or both. Empty returns both. United States and Australia only: the public actor refuses a UK or Canadian request and stops the run with an error, so no other value is accepted.
sourcesNoDirectories to read. Empty reads every implemented source. Sources that are not implemented yet, or that the actor does not cover, are skipped and named in the RUN_SUMMARY record. The 18 implemented sources are abime, lacourt-panels, sfbar, cccba, isba, lsba, aaimco, medilaw, lexmedicus, aushub, medicolegal-specialists, index-medicolegal, themis, integrityml, vmls, lime, mag-directory, workcover-wa.
maxItemsNoStop after this many output rows (one row per deduplicated expert). 0 means no cap. A capped run never marks listings as removed. Default: 100.
specialtyNoTaxonomy codes. A parent code also matches its children: medicine.psychiatry includes medicine.psychiatry.forensic. Empty returns every specialty.
verifyNppesNoCheck each US record against the free NPPES monthly file (name, state, and specialty). Adds npi and nppes_status. NPPES carries no email. Charged per checked record. Default: false.
persistStoreNameNoNamed key-value store in your account that keeps expert records between runs. Reuse the same name for feed mode. Default: expert-witness-directory-store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: APIFY_TOKEN requirement, Apify credit consumption, per-record and per-email pricing, per-run NPPES verification charges, the refusal on UK/Canadian input that halts the run, the guarantee that published_email is never guessed, and the source terms-of-service caveat. Annotations already declare readOnly/openWorld, but the description carries rich operational context on top.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, which is good, but the body is a dense block mixing pricing, terms posture, auth, and parameter recap; several statements (country refusal, mode definitions) duplicate the schema. Every sentence is informative but the size is heavier than needed for the selection decision.

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?

With no output schema, the description fully carries the burden: it enumerates the returned fields (name, specialty, state/region, country, firm, practice site, phone, listing URL, sources), covers the error behavior, auth, and cost model. An agent has everything required to call and interpret it correctly.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining why country is limited to US/AU, how published_email is populated, and the semantics and cost implications of mode and verifyNppes. It adds meaning but also repeats several schema-documented points.

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?

States a concrete verb and resource ('Find expert witnesses and medico-legal assessors') and constrains the geography to the US and Australia immediately. It also signals the aggregation/dedup/taxonomy behavior, so an agent knows exactly what kind of search this is. No siblings exist to distinguish from, but the purpose is 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?

Gives clear context for when each mode applies ('mode list returns every matching expert; mode feed returns only experts new, changed, returned, or removed since the last run') and warns that country is US/AU only. It stops short of explicit when-not-to-use or alternative-tool routing (none exist), so it is clear context without exclusions.

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

Deploy Server

Other Tools