Skip to main content
Glama

UK Legal Research

by io.github.paulieb89

Get Committee Detail

committees_get_committee
Read-onlyIdempotent

USE THIS TOOL WHEN you have a committee_id and want the metadata + current membership.

Fetches committee detail and member list in parallel. AFTER calling, pass committee_id into committees_search_evidence to see what evidence has been submitted to this committee on what topics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
committee_idYesCommittee ID from committees_search_committees results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCommittee ID
urlNoParliament URL for this committee
nameYesCommittee name
emailNoContact email
houseNoCommons, Lords, or Joint
phoneNoContact phone number
membersNoCurrent committee members

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / committee_id
      Added value: +{
+  "description": "Committee ID from committees_search_committees results.",
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / params
      Removed value: -{
-  "additionalProperties": false,
-  "description": "CommitteeDetailInput.",
-  "properties": {
-    "committee_id": {
-      "description": "Committee ID from committees_search_committees results.",
-      "minimum": 1,
-      "type": "integer"
-    }
-  },
-  "required": [
-    "committee_id"
-  ],
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "params"
-]New value: +[
+  "committee_id"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"CommitteeDetailInput with committee_id from committees_search_committees."New value: +"CommitteeDetailInput."
  3. Changed1 schema field changed
    • addedInput schema / properties / params / description
      Added value: +"CommitteeDetailInput with committee_id from committees_search_committees."
  4. Changed11 schema fields changed
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
    • addedOutput schema / properties / email
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Contact email"
+}
    • addedOutput schema / properties / house
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Commons, Lords, or Joint"
+}
    • addedOutput schema / properties / id
      Added value: +{
+  "description": "Committee ID",
+  "type": "integer"
+}
    • addedOutput schema / properties / members
      Added value: +{
+  "description": "Current committee members",
+  "items": {
+    "properties": {
+      "name": {
+        "description": "Member display name",
+        "type": "string"
+      },
+      "party": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Political party"
+      },
+      "role": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Role on the committee (e.g. 'Chair')"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / name
      Added value: +{
+  "description": "Committee name",
+  "type": "string"
+}
    • addedOutput schema / properties / phone
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Contact phone number"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / url
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Parliament URL for this committee"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "id",
+  "name"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, lowering the burden. The description adds valuable behavioral context by noting that committee detail and member list are fetched in parallel, and it reveals the intended follow-up workflow. This goes beyond simple safety disclosure, though it doesn't detail response structure or pagination (which are covered by the output schema).

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

Conciseness5/5

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

The description is compact and front-loaded with the key usage condition, followed by the action and a next-step suggestion. Every sentence provides distinct value with no 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 single-parameter get-by-ID tool with rich annotations and an output schema, the description fully covers the necessary context: when to use it, what it returns, and what to do next. The workflow hint to committees_search_evidence completes the contextual picture.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter committee_id is already well-described in the schema as coming from committees_search_committees results. The description does not add additional semantic meaning beyond that, so the baseline of 3 is appropriate.

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?

The description clearly states this tool fetches committee detail and member list, with an explicit 'USE THIS TOOL WHEN...' condition. It distinguishes itself from sibling search tools by requiring a committee_id and focusing on metadata + membership.

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?

The description provides explicit when-to-use guidance ('when you have a committee_id and want metadata + current membership') and adds a workflow pointer to committees_search_evidence. However, it does not explicitly state when not to use it or name alternative tools for lookup scenarios, so it stops short of a 5.

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

All UK Legal Research toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Tools covering similar domains (e.g., multiple parliament search tools) are carefully differentiated by their search approach and input requirements.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., bills_get_bill, case_law_search, citations_resolve). Even generic tools adhere to this style. No mixing of conventions.

Tool Count4/5

With 35 tools, the count is on the higher side but appropriate for the wide-ranging domain of UK legal research. Each tool contributes to specific sub-domains (bills, case law, citations, committees, HMRC, legislation, parliament, votes) without unnecessary duplication.

Completeness5/5

The tool surface covers nearly all essential aspects of UK legal research: searching and retrieving bills, case law, and legislation; parsing and resolving citations; exploring committee evidence; accessing Hansard debates and member interests; and checking HMRC guidance and VAT rates. Gaps like full judgment text retrieval are mitigated by paragraph-level access and indexing.

Resources