Schema | AI Incident Law

AI Incident Law

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
list_datasetsA	Summarize the available AI Incident Law dataset buckets and record counts.
list_recordsB	List compact AI incident law records, optionally filtered by dataset, domain, type, jurisdiction, status, source quality, or review flag.
get_recordA	Get one full AI Incident Law source record by error_id or candidate_id.
search_recordsB	Search across record titles, descriptions, parties, jurisdictions, tags, and source metadata.
get_staleness_reportA	Report record verification decay: records ranked oldest-verified first, with per-bucket counts. Use to find matters overdue for re-verification before relying on them.
list_authoritiesB	List Obligation-First authority records generated from included public matters.
get_authorityC	Get a generated Obligation-First authority record by authority ID.
get_obligation_first_recordB	Get a generated Obligation-First proceeding, allegation, determination, or authority record by kind and ID.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/snapsynapse/ai-incident-law'

If you have feedback or need assistance with the MCP directory API, please join our Discord server