Skip to main content
Glama

Server Details

MCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
thechancerylaneproject/tclp-mcp
GitHub Stars
0
ChatGPT
–
Claude
The Chancery Lane Project

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct retrieval mode: semantic search, deterministic entity name matching, legal-instrument listing, single legal-instrument retrieval, taxonomy vocabulary discovery, and facet-filtered listing. The descriptions explicitly contrast overlapping pairs (entity_lookup vs search, find_legal_resources vs search). The only real overlap is that taxonomy_content(scope="legal_resource") can surface the same instruments find_legal_resources returns, which could cause occasional misselection.

Naming Consistency4/5

Three tools follow a clean verb_noun pattern (entity_lookup, find_legal_resources, get_legal_resource) and the two taxonomy tools form a coherent namespace-prefixed pair. The bare `search` verb is the main deviation from the convention, but overall the naming is predictable and readable.

Tool Count5/5

Six tools is well-scoped for a read-only knowledge graph covering content search, entity lookup, legal resources, and taxonomy navigation. Each tool has a distinct role and none feels redundant or vestigial.

Completeness4/5

The surface covers the core read paths: discovery (search, entity_lookup, taxonomy_facets), filtering (taxonomy_content), and legal resource list/detail (find_legal_resources + get_legal_resource). The notable gap is that content items expose `id`/`url` in results but there is no get_content-by-id fetch, so retrieving a specific clause or guide requires a round trip through search or a facet listing.

Available Tools

6 tools
entity_lookupA
Read-only
Inspect

Find TCLP content (clauses, glossary terms, guides) associated with a named concept.

Unlike `search`, this performs a deterministic name match against Entity nodes in
the knowledge graph rather than a relevance-ranked semantic search. Use it when
you have a specific term or concept (e.g. "scope 3 emissions", "net zero") and
want to retrieve every clause or glossary entry that explicitly references it.

Args:
    name: The entity or concept name to look up (exact match, case-insensitive).
    limit: Maximum number of results to return (1–50).
    include_full_text: Include each hit's full body text (Markdown). Off by
        default — bodies are large; request only when you need the content,
        and prefer a small `limit` when you do.

Returns:
    JSON with "meta" and "results" where each hit includes the source content
    node, its plain-text `summary` (null when it has none), its `child_name`
    (a clause's child name, null otherwise) and the entity names that matched.
    Each hit's "references" lists the instruments it cites: pass a
    reference's `work_id` to `get_legal_resource` for details. A reference's
    `edge` (governs, references, describes) says how the content relates to
    the instrument; it is not a statement of the instrument's legal effect.
    An empty list means the hit cites no instruments. null with "lrsf" in
    meta.degraded means references could not be loaded: do not conclude
    that the hit cites no instruments.

Inputs: name (required), limit, include_full_text. Returns: meta, results

taxonomy_contentA
Read-only
Inspect

List TCLP content (clauses, guides) or legal resources filtered by taxonomy facet=value.

Multi-facet filters are combined with AND. Call `taxonomy_facets` first
to learn which facet names and slugs exist; using a name not in that
list returns a 400.

Args:
    filters: Mapping of facet name to value slug, e.g.
             `{"sector": "real-estate", "practice_area": "commercial"}`.
             Each facet may appear at most once.
    scope: `clause` (ClauseName only), `guide` (Guide only), `legal_resource`
           (laws, regulations, standards and frameworks; facets `jurisdiction`
           and `sector` only), or `all` (clauses and guides, the default).
    limit: Maximum results to return (1–100, default 25).
    offset: Result offset for paging (default 0).
    sort: `title`, `date_published_desc`, or `date_modified_desc`.

Returns:
    JSON with "meta" (totals, scope, filters echoed back) and "results"
    (each hit has `id`, `url`, `title`, `content_type`, dates,
    `summary` (the clause summary or guide excerpt as plain text, null for
    legal resources), `child_name` (a clause's child name, e.g. "Odhran's
    Clause", null otherwise), and a
    `facets` map of all taxonomy arrays on the node). `content_type` is
    `clause`, `guide` or `legal_resource`, the same values that `search`
    returns.

Inputs: filters (required), sort, limit, scope, +1 more. Returns: meta, results

taxonomy_facetsA
Read-only
Inspect

List taxonomy facets and their value slugs across TCLP content.

Facets are taxonomy categories like `sector`, `practice_area`,
`application`, and `jurisdiction`. Each facet returns the list of slugs
that actually appear on the graph, with counts. Use this to discover
the vocabulary, then call `taxonomy_content` with chosen slugs.

Args:
    scope: Which labels to include — `clause` (ClauseName only), `guide`
           (Guide only), `legal_resource` (laws, regulations, standards and
           frameworks; facets `jurisdiction` and `sector` only), or `all`
           (clauses and guides, the default).

Returns:
    JSON with "meta" and "facets". Each facet has `name`, `applies_to`
    (list of Neo4j labels carrying it), and `values` (list of
    `{slug, count}`, sorted by count desc).

Inputs: scope. Returns: meta, facets

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that connects GraphDB's SPARQL endpoints and Ollama models to Claude, enabling Claude to query and manipulate ontology data while leveraging various AI models.
      28
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for building knowledge graphs from documents. It ingests PDF/PPTX/DOCX files, transcribes to Markdown, and uses LLM to bootstrap entity patterns and build a JSONL knowledge graph with RAG chunks.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.