Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PH_COMPLIANCE_LOCAL_CORPUSNoPath to a local corpus directory for air-gapped deployments. If not set, corpus assets are downloaded and cached under ~/.cache/ph-compliance-mcp.

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
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_statuteA

Lexical (FTS5/BM25) search over the statute corpus (Constitution, codes, RA, PD, EO). Information retrieval, not legal advice. Results carry structured citations; below confidence threshold the tool reports insufficient corpus coverage rather than guessing.

Pagination: use offset to page; check hasMore/nextOffset. Use domain to narrow results.

search_jurisprudenceA

Lexical (FTS5/BM25) search over the case corpus (SC, CA, SB, CTA decisions). Information retrieval, not legal advice. Results carry structured citations; below confidence threshold the tool reports insufficient corpus coverage rather than guessing.

Pagination: use offset to page; check hasMore/nextOffset. Use court to narrow results.

search_issuanceA

Lexical (FTS5/BM25) search over the administrative issuance corpus (BIR first, Phase 3). Information retrieval, not legal advice. Below confidence threshold it reports insufficient corpus coverage rather than guessing.

Pagination: use offset to page; check hasMore/nextOffset. Filter by agency or issuanceType.

get_provisionA

Return the exact text of a provision (e.g. Civil Code Art. 1156) with its current status. Version-aware: reports amended/repealed/superseded status when the corpus tracks it.

get_caseA

Return a case by citation (e.g. 'G.R. No. 238875') with metadata and the first passages of the decision.

get_issuanceA

Return an issuance by agency + reference number (e.g. 'BIR' / 'RMC 85-2023') with metadata and the first passages of the document.

cite_validateA

Resolve a citation against the corpus and return the exact matching text. If the citation cannot be resolved, it returns a clear 'cannot validate' verdict — it never fills in plausible text. Use this before relying on any AI-generated citation.

list_domainsA

Enumerate the 15-domain compliance taxonomy (ADR-000 core + ADR-004 expansion) with corpus refresh timestamps, so callers can check freshness before trusting retrieval results.

related_lawsA

Given a case citation (G.R. No.), list the statutes that case cites, resolved against the corpus. Only citations that resolve to an ingested statute are returned.

related_casesA

Given a case citation, find other cases in the corpus that cite at least one of the same statutes (shared citation neighborhoods). Useful for identifying lines of jurisprudence.

show_amendmentsA

List the amendment log for a statute (amending law, affected provision, effective date). Use with get_provision to confirm the current text of an amended provision.

show_historyA

Show every recorded version of a provision, ordered by effective date (valid_from). Confirms whether the current text differs from an earlier version.

show_dependenciesA

Show which statutes a statute cites (dependencies) and which statutes cite it back (dependentOn), from corpus-grounded law→law edges.

show_citationsA

List every citation a case makes (statutes and other cases), as recorded in the citation graph. Citations that could not be resolved against the corpus are not listed.

show_implementing_rulesA

Find corpus references to the Implementing Rules and Regulations (IRR) of a statute — citations mentioning IRR that resolve to the statute, with the citing cases.

show_cross_referencesB

Curated cross-domain references (from the domain registry) for the statute's domain, plus statute→statute citation edges from the corpus graph.

compute_prescriptionA

Deterministic prescriptive-period calculator under Civil Code Arts. 1144-1149 (RA 386). Pick the class of action to get the codal period in years, the exact article, and — if a cause-of-action date is given — the computed deadline. The computation is arithmetic over the cited articles; verify the codal text with get_provision or cite_validate before relying on it, and note that interruption (Art. 1155) can extend the deadline in practice. Not legal advice.

compute_deadlineA

Deterministic filing-deadline calculator under the Rules of Court. Applies Rule 22 computation of time (exclude the first day, include the last; last day on a Saturday, Sunday, or legal holiday runs to the next working day) to the common reglementary periods (Rule 37, Rule 41, Rule 45, Rule 65). Pass legal holidays as ISO dates — they are declared per year by proclamation, so never assume the calendar. Verify the rule text with get_provision or cite_validate before relying on it. Not legal advice.

compute_13th_monthA

Deterministic 13th-month-pay calculator under PD 851 (as amended by Memorandum Order No. 28 and the Rules Implementing PD 851). Computes total basic salary earned within the calendar year ÷ 12 for rank-and-file employees (pro-rated automatically for partial-year service), and returns coverage/exclusion notes plus the payment deadline (on or before December 24). Verify the rule text and current DOLE advisories with the corpus before relying on it. Not legal advice.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Law domains indexThe 15-domain compliance taxonomy (ADR-000 core + ADR-004 expansion) with corpus freshness timestamps

TDQS

A4.1/5.0

Scored across 19 tools

Disambiguation5/5

Each tool targets a distinct resource or action: search across three corpora, get by citation, relationship/neighborhood tools (related_laws vs. related_cases vs. show_dependencies vs. show_citations), versioning (show_amendments vs. show_history), and three separate deterministic calculators. Any overlap is narrow and the descriptions clarify the boundaries.

Naming Consistency4/5

The vast majority follow a verb_noun snake_case pattern (search_, get_, show_, compute_, list_). Minor deviations: 'related_laws' and 'related_cases' use an adjective prefix, and 'cite_validate' inverts the expected verb order (validate_citation). These are still readable and predictable.

Tool Count4/5

At 19 tools, this sits in the 16-25 'heavy but borderline' range. Given the multi-corpus scope (statutes, jurisprudence, issuances) plus citation graph, versioning, and computation tools, each tool has a unique role and the count is defensible, though a slightly tighter set could be imagined.

Completeness5/5

The surface covers the full lifecycle for a read-only compliance server: search across all corpora, exact retrieval by citation, citation validation, relationship exploration (dependencies, citations, IRRs, cross-references), version/amendment tracking, and deterministic computations for key deadlines. No obvious dead ends or missing operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues