Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

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.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld.

get_authorityB

Get a generated Obligation-First authority record by authority ID, not a source matter ID. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld.

get_obligation_first_recordB

Get a generated Obligation-First authority, proceeding, allegation, determination, or tombstone record by kind and graph ID. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld. A proceeding or allegation does not establish a determination.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation3/5

Most tools have distinct purposes (list vs search vs get), and descriptions clarify source vs generated records. However, get_authority clearly overlaps with get_obligation_first_record, since the latter explicitly handles 'authority' records by kind and graph ID, creating real ambiguity about which to use for an authority. list_authorities vs list_records is milder but also potentially confusable.

Naming Consistency5/5

All eight tool names use consistent snake_case with a verb_noun pattern (get_, list_, search_). Compound nouns vary in length but the convention is uniform throughout.

Tool Count5/5

Eight tools is well-scoped for a specialized legal/incident data server. Each tool covers a distinct capability (datasets, listing, search, source retrieval, authority retrieval, staleness) and none feels redundant beyond the noted authority overlap.

Completeness4/5

The read surface is solid: dataset summaries, filtered listing, full-text search, source record retrieval, generated record retrieval, and a staleness/verification report. It lacks explicit pagination or enumeration helpers (e.g. list jurisdictions/domains) but core discovery and retrieval workflows are covered with no dead ends.

Maintenance

ActivityActive
ResponsivenessNo issues