Skip to main content
Glama
Sign In

tclp-mcp

by io.github.thechancerylaneproject
OverviewDiscussionsAdmin

taxonomy_content

Read-only

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), 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.

Input Schema

NameRequiredDescriptionDefault
sortNotitle
limitNo
scopeNoall
offsetNo
filtersYes

Output Schema

NameRequiredDescriptionDefault
metaYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / _TaxonomyContentHit / properties / summary
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Summary"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "clause",
+  "guide",
+  "legal_resource",
+  "all"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "title",
+  "date_published_desc",
+  "date_modified_desc"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "_TaxonomyContentHit": {
+      "properties": {
+        "content_type": {
+          "title": "Content Type",
+          "type": "string"
+        },
+        "date_modified": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Date Modified"
+        },
+        "date_published": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Date Published"
+        },
+        "facets": {
+          "additionalProperties": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": "Facets",
+          "type": "object"
+        },
+        "id": {
+          "title": "Id",
+          "type": "string"
+        },
+        "title": {
+          "title": "Title",
+          "type": "string"
+        },
+        "url": {
+          "title": "Url",
+          "type": "string"
+        }
+      },
+      "title": "_TaxonomyContentHit",
+      "type": "object"
+    },
+    "_TaxonomyContentMeta": {
+      "properties": {
+        "filters": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "title": "Filters",
+          "type": "object"
+        },
+        "request_id": {
+          "title": "Request Id",
+          "type": "string"
+        },
+        "scope": {
+          "title": "Scope",
+          "type": "string"
+        },
+        "took_ms": {
+          "title": "Took Ms",
+          "type": "integer"
+        },
+        "total_available": {
+          "title": "Total Available",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "total_available",
+        "took_ms",
+        "request_id",
+        "scope",
+        "filters"
+      ],
+      "title": "_TaxonomyContentMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "meta": {
+      "$ref": "#/$defs/_TaxonomyContentMeta"
+    },
+    "results": {
+      "items": {
+        "$ref": "#/$defs/_TaxonomyContentHit"
+      },
+      "title": "Results",
+      "type": "array"
+    }
+  },
+  "required": [
+    "meta",
+    "results"
+  ],
+  "title": "TaxonomyContentResult",
+  "type": "object"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations only covering the safety profile, the description adds substantial behavior: multi-facet filters combine with AND, each facet may appear at most once, invalid facet names return 400, and scope=legal_resource silently restricts usable facets to jurisdiction and sector. These are non-obvious constraints an agent could not infer from the annotations or schema.

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

Conciseness4/5

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

Front-loaded with purpose, then cleanly sectioned into Args and Returns; every line is content-bearing. The Returns block is somewhat lengthy and partially overlaps with the existing output schema, which is mild redundancy.

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?

For a multi-parameter, nested-object, paged query tool, the description covers inputs, scope semantics, error conditions, and result shape, so an agent has everything needed to invoke it correctly. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it explains filters as a facet-name-to-slug map with an example, defines each scope enum value and its facet restrictions, gives limit bounds and default, offset paging, and the meaning of each sort value.

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 specific verb (list) plus the resources covered (TCLP clauses, guides, legal resources) and the filtering mechanism (taxonomy facet=value). This clearly separates it from sibling tools like search and find_legal_resources, which are not facet-driven listings.

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 an explicit prerequisite workflow ('Call taxonomy_facets first') and the failure mode if ignored (400 on unknown facet name), which is strong usage guidance. It does not, however, state when to prefer this over the sibling search tool, so it falls short of full alternative routing.

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

All tclp-mcp toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources