io.github.paulieb89/uk-legal-mcp

Est-ce que io.github.paulieb89/uk-legal-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.paulieb89/uk-legal-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 35 outils

• bills_get_bill≈ 965 tokens

  USE THIS TOOL WHEN you have a bill_id (from bills_search_bills) and want the full detail. Returns sponsors, current stage, long title, summary, and Royal Assent date if enacted. Summary text is capped per max_summary_chars — check summary_truncated in the response. AFTER calling, use parliament_search_hansard(query=bill_short_title) to find the bill's parliamentary debates, or bills_search_bills with a related keyword for adjacent bills.

  Paramètres, retour & exemple (2)

  Paramètres

  • bill_id · integer · requis
    Bill ID from bills_search_bills results.
  • max_summary_chars · integer · optionnel
    Maximum characters of the bill summary text to return. Default 5,000 (~1,250 tokens) covers most bills. Raise for substantive government bills (Finance Act, Levelling-up) whose summary runs longer. Check summary_truncated in the response to see if it was cut.

  Exemple d'appel

  {"name": "bills_get_bill", "arguments": {"bill_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "url": "texte", "is_act": true, "stages": [], "summary": "texte", "sponsors": [], "long_title": "texte", "short_title": "texte", "current_house": "texte", "current_stage": "texte", "originating_house": "texte", "royal_assent_date": "texte"}}

• bills_search_bills≈ 1073 tokens

  USE THIS TOOL WHEN searching UK parliamentary bills by keyword, session, house, or legislative stage. Returns a paginated page of bill summaries (title, originating and current house, current stage, whether it became an Act). AFTER calling, pass a bill_id into bills_get_bill for full detail (sponsors, long title, Royal Assent date). Authoritative source for UK parliamentary bill status.

  Paramètres, retour & exemple (6)

  Paramètres

  • house · ? · optionnel
    Filter by originating house: the House the bill was introduced in, wherever it sits now. Omit (or 'All') for all houses.
  • limit · integer · optionnel
    Maximum bills to return in this call. Default 20 keeps responses focused; raise up to 100 for bulk exports.
  • query · string · requis
    Search term for bill titles and descriptions, e.g. 'online safety' or 'financial services'.
  • stage · ? · optionnel
    Filter by current legislative stage.
  • offset · integer · optionnel
    Number of results to skip before this page. Default 0 for the first page. Re-call with offset=offset+returned while has_more is true to paginate.
  • session · ? · optionnel
    Numeric parliamentary session ID (e.g. 40 = 2024-25, 39 = 2023-24). NOT a year string like '2025'. If you only know the year, omit this and filter the results instead. Omit to search all sessions.

  Exemple d'appel

  {"name": "bills_search_bills", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"bills": [], "limit": 1, "query": "texte", "total": "texte", "offset": 1, "has_more": true, "returned": 1}}

• case_law_grep_judgment≈ 664 tokens

  USE THIS TOOL WHEN you have a judgment slug and want to find paragraphs whose text matches a pattern. Returns a list of `{eId, snippet, match}` hits — small per-paragraph snippets centred on the match. AFTER calling, read full paragraphs via judgment_get_paragraph(slug, eId) or the judgment://{slug}/para/{eId} resource. Use case: content search within one judgment (e.g. "negligence", "test for foreseeability", "Donoghue"). For paragraph-number navigation by eId, call judgment_get_index instead. Pattern is regex; if it doesn't compile, falls back to literal substring search.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · requis
    TNA judgment slug, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450'.
  • pattern · string · requis
    Regex pattern (or plain substring) to search within paragraph text. If the pattern doesn't compile as regex, falls back to literal substring match.
  • max_hits · integer · optionnel
    Cap on number of hits returned.
  • case_insensitive · boolean · optionnel
    Default true. Set false for case-sensitive matching.

  Exemple d'appel

  {"name": "case_law_grep_judgment", "arguments": {"slug": "texte", "pattern": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"hits": [], "slug": "texte", "pattern": "texte", "truncated": true}}

• case_law_search≈ 1576 tokens

  USE THIS TOOL WHEN searching UK case law by party names, court, judge, date, or free-text query. Returns paginated judgment summaries: neutral citation, court, dates, slug, stable TNA URI. AFTER calling: pass slug into judgment_get_header / judgment_get_index / judgment_get_paragraph (or the judgment:// resource family) for content; pass the neutral citation into citations_resolve to verify before constructing an OSCOLA citation; use case_law_grep_judgment to find text within a single judgment. When a party name returns several candidates, narrow with court + year filters before grep-iterating across full judgments — targeted filtering beats scanning every candidate. Coverage: TNA Find Case Law indexes UK judgments from roughly the early 2000s onwards. For older authorities, search for a modern judgment that quotes them and read that paragraph. Authoritative source for UK case law. Web search returns out-of-date or unstable URLs — do not supplement.

  Paramètres, retour & exemple (8)

  Paramètres

  • page · integer · optionnel
    Result page number (1-indexed)
  • court · ? · optionnel
    Filter by court slug. Values: 'uksc', 'ukpc', 'ewca/civ', 'ewca/crim', 'ewhc/kb', 'ewhc/ch', 'ewhc/comm', 'ewhc/fam', 'ewhc/pat', 'ewhc/ipec', 'ewhc/admin', 'ewhc/tcc', 'ewhc/costs', 'ewfc', 'ewcop', 'eat', 'ukut/iac', 'ukut/aac', 'ukut/tcc', 'ukut/lc', 'ukftt/tc', 'ukftt/grc', 'nica', 'niqb'.
  • judge · ? · optionnel
    Filter by judge surname. Case-insensitive substring match against the indexed form. Use the surname alone ('Reed', 'Sumption') or with the bare title ('Lord Reed'). Honorific suffixes silently zero the result set — do not append 'JSC', 'of Allermuir', 'KC' etc. Speculating a fuller form than what TNA indexed will return 0 hits with no error.
  • limit · integer · optionnel
    Maximum results to return (1–50). TNA returns up to 50 per request; this slices client-side. Default 10 for a tight shortlist. Set higher for breadth (e.g. 50 to scan the full result set).
  • party · ? · optionnel
    Filter by party name
  • query · string · requis
    Full-text search query, e.g. 'negligence duty of care'
  • to_date · ? · optionnel
    Latest judgment date (YYYY-MM-DD). Same caveat as `from_date` — currently silently ignored by upstream. Filtering happens client-side at best.
  • from_date · ? · optionnel
    Earliest judgment date (YYYY-MM-DD). NOTE: the TNA atom.xml endpoint currently appears to ignore this filter — the same results come back regardless. Do not rely on it to narrow output; sort+slice client-side or refine `query` instead.

  Exemple d'appel

  {"name": "case_law_search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "results": [], "has_more": true, "total_pages": "texte"}}

• citations_format_oscola≈ 922 tokens

  USE THIS TOOL AFTER citations_resolve to produce the correctly formatted OSCOLA citation string. Pass the parsed fields returned by citations_resolve directly into this tool. Formats per OSCOLA 4th edition rules for each citation type. Refuses (status: upstream_validation) if confidence is 0.0 — TNA confirmed the document does not exist — or if a neutral citation has no resolved_url (ambiguous court code, e.g. bare EWHC without a division). In either case, do NOT manufacture a citation; surface the failure and ask the user for the source URL or better identifying details. DO NOT construct the input fields yourself. The structured input must come from citations_resolve — guessing fields is the primary citation-fabrication route and this tool is the guard against it. Authoritative OSCOLA formatting for UK legal citations (no network call).

  Paramètres, retour & exemple (14)

  Paramètres

  • raw · ? · optionnel
    'raw' from citations_resolve. Used as-is for EU retained law — the original text preserves the Regulation/Directive distinction.
  • page · ? · optionnel
    'page' from citations_resolve (starting page in the law report).
  • year · ? · optionnel
    'year' from citations_resolve.
  • court · ? · optionnel
    'court' from citations_resolve, e.g. 'UKSC', 'EWCA CIV', 'EWHC (KB)'.
  • number · ? · optionnel
    'number' from citations_resolve (judgment number within the year).
  • volume · ? · optionnel
    'volume' from citations_resolve (law report volume, if any).
  • section · ? · optionnel
    'section' from citations_resolve, e.g. '47', '12', '20A'.
  • si_year · ? · optionnel
    'si_year' from citations_resolve.
  • si_number · ? · optionnel
    'si_number' from citations_resolve.
  • confidence · number · requis
    'confidence' from citations_resolve. Refuses to format if 0.0 — that means TNA confirmed the document does not exist. Pass only the value citations_resolve returned; do not guess.
  • resolved_url · ? · optionnel
    'resolved_url' from citations_resolve. Must be non-null for neutral citations.
  • citation_type · string · requis · neutral | law_report | legislation | si | eu_retained
    'type' field from citations_resolve result.
  • report_series · ? · optionnel
    'report_series' from citations_resolve, e.g. 'WLR', 'AC', 'QB'.
  • legislation_title · ? · optionnel
    'legislation_title' from citations_resolve, e.g. 'Companies Act 2006'.

  Exemple d'appel

  {"name": "citations_format_oscola", "arguments": {"confidence": 1, "citation_type": "neutral"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• citations_network≈ 598 tokens

  USE THIS TOOL WHEN you have a judgment slug and want to map every citation it makes — cases cited, legislation referenced, SIs, retained EU law. Fetches the judgment XML from TNA and parses all OSCOLA citations within. Returns citations grouped by type, deduplicated and sorted. AFTER calling, pass any individual citation through citations_resolve to confirm it resolves and to retrieve its canonical URL. Useful for authority-network analysis (what did this judgment rely on?) and for surfacing the legislative landscape a case sits inside.

  Paramètres, retour & exemple (1)

  Paramètres

  • case_uri · string · requis
    TNA judgment URI slug, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450'. Use the 'uri' field from case_law_search results — not the full URL. Do not include the 'https://caselaw.nationalarchives.gov.uk/' prefix.

  Exemple d'appel

  {"name": "citations_network", "arguments": {"case_uri": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"eu_refs": [], "si_refs": [], "case_uri": "texte", "law_report_refs": [], "total_citations": 1, "legislation_refs": [], "neutral_citations": []}}

• citations_parse≈ 1791 tokens

  USE THIS TOOL WHEN you have free text (a memo, an email, a clause) and want every OSCOLA-style citation it contains extracted and classified. Identifies: neutral citations ([2024] UKSC 12), law reports ([2024] 1 WLR 100), legislation sections (s.47 Companies Act 2006), SIs (SI 2018/1234), retained EU law (Regulation (EU) 2016/679). Parsing is pure regex by default. Ambiguous citations (e.g. bare [2024] EWHC without division) can OPTIONALLY be disambiguated by setting disambiguate=True, which asks the CONNECTED CLIENT's own model (not this server) to resolve the division via MCP sampling — off by default. Citations resolve to TNA / legislation.gov.uk URLs when possible. AFTER calling, pass each citation through citations_resolve to verify it points at a real document before quoting or formatting it — the parser recognises the SHAPE of a citation but does not confirm the document exists.

  Paramètres, retour & exemple (2)

  Paramètres

  • text · string · requis
    Free text containing OSCOLA citations to extract. Supported: neutral citations ([2024] UKSC 12), law reports ([2024] 1 WLR 100), legislation sections (s.47 Companies Act 2006), SIs (SI 2018/1234), retained EU law (Regulation (EU) 2016/679). Max 50,000 chars.
  • disambiguate · boolean · optionnel
    Default False — pure-regex parsing, no model in the loop. If True, ambiguous citations (e.g. bare EWHC without a division) are sent to the connected client's own LLM, via MCP sampling, to resolve the division. Opt in only when you want best-effort division resolution and accept that a model shapes the result.

  Exemple d'appel

  {"name": "citations_parse", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ambiguous": [], "citations": [], "text_length": 1, "parse_duration_ms": 1}}

• citations_resolve≈ 951 tokens

  USE THIS TOOL BEFORE constructing an OSCOLA citation string from known fields, OR to confirm a citation points at a real document. Parses + resolves a single citation (neutral citation, SI, legislation section, retained EU law) and returns parsed fields plus resolved_url. For neutral citations, performs a live TNA HEAD check — non-200 sets confidence to 0.0 (document absent). Do NOT format or quote a confidence-0.0 citation. If the TNA HEAD check fails (timeout, connection error), raises ToolError with {"error_category": "transient", "is_retryable": true}. One retry is attempted — retry this call or proceed without TNA verification. Formatting a citation from "known" fields without prior resolution is the most common fabrication route. If this tool raises or returns no resolved_url, do NOT manufacture a citation — surface the failure and ask the user for the source URL. Authoritative source for UK legal-citation resolution.

  Paramètres, retour & exemple (1)

  Paramètres

  • citation · string · requis
    A single OSCOLA citation to parse and resolve. E.g. '[2024] UKSC 12', 'SI 2018/1234', 's.47 Companies Act 2006'

  Exemple d'appel

  {"name": "citations_resolve", "arguments": {"citation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"raw": "texte", "page": "texte", "type": "neutral", "year": "texte", "court": "texte", "number": "texte", "volume": "texte", "section": "texte", "si_year": "texte", "si_number": "texte", "confidence": 1, "resolved_url": "texte"}}

• committees_get_committee≈ 468 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • committee_id · integer · requis
    Committee ID from committees_search_committees results.

  Exemple d'appel

  {"name": "committees_get_committee", "arguments": {"committee_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "url": "texte", "name": "texte", "email": "texte", "house": "texte", "phone": "texte", "members": []}}

• committees_search_committees≈ 702 tokens

  USE THIS TOOL WHEN searching or listing UK parliamentary select committees by name, house, or active status. Returns committee summaries (name, house, active status, ID). AFTER calling, pass committee_id into committees_get_committee for current membership, or into committees_search_evidence to retrieve oral and written evidence submitted to that committee.

  Paramètres, retour & exemple (4)

  Paramètres

  • house · ? · optionnel
    Filter by house.
  • limit · integer · optionnel
    Maximum committees to return. Default 100 comfortably covers all currently-active UK select committees. Raise only for historical sweeps.
  • query · ? · optionnel
    Search term for committee names, e.g. 'defence' or 'treasury'. Filtered client-side against committee names. Omit to list all committees.
  • active_only · boolean · optionnel
    If true, only return currently active committees.

  Exemple d'appel

  {"name": "committees_search_committees", "arguments": {"house": "texte", "limit": 1, "query": "texte", "active_only": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"house": "texte", "query": "texte", "total": 1, "committees": [], "active_only": true}}

• committees_search_evidence≈ 1282 tokens

  USE THIS TOOL WHEN you have a committee_id and want the oral and written evidence submitted to it. Returns ONE PAGE of evidence (default 20) plus `total`, the source's count of matching items. evidence_type='both' lists all oral evidence first, then all written evidence, each newest-published first as the source orders it. Free-text titles are capped per max_title_chars; witness lists are capped at 10 per item. An organisation witness (no named individual) is rendered as '<Organisation> (<Role>)'; a null entry means the source gave no name for that witness at all. For committees with many submissions, re-call with offset=offset+returned while has_more is true. Authoritative source for parliamentary committee evidence.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Maximum evidence items to return. Default 20. For evidence_type='both' a page may hold only oral, only written, or the last oral items followed by the first written items.
  • offset · integer · optionnel
    Number of evidence items to skip before this page. Default 0. Re-call with offset=offset+returned while has_more is true. For evidence_type='both' this is a position in the combined sequence (all oral evidence, then all written evidence).
  • committee_id · integer · requis
    Committee ID from committees_search_committees results.
  • evidence_type · string · optionnel · oral | written | both
    Type of evidence to search.
  • max_title_chars · integer · optionnel
    Per-item cap on the free-text title field. Default 300 prevents context blow-up from verbose inquiry titles. Raise to 1000+ only when you need the full title text.

  Exemple d'appel

  {"name": "committees_search_evidence", "arguments": {"committee_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "total": 1, "offset": 1, "evidence": [], "has_more": true, "returned": 1, "committee_id": 1, "evidence_type": "oral"}}

• get_prompt≈ 220 tokens

  Get a prompt by name with optional arguments. Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    The name of the prompt to get
  • arguments · ? · optionnel
    Optional arguments for the prompt

  Exemple d'appel

  {"name": "get_prompt", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• hmrc_check_mtd_status≈ 406 tokens

  USE THIS TOOL WHEN you have a 9-digit VAT Registration Number and need that business's Making Tax Digital VAT mandate status. Returns whether the business is mandated for MTD, effective date, and trading name. Connects to the HMRC sandbox by default. Set HMRC_API_BASE to 'https://api.service.hmrc.gov.uk' for production. Requires HMRC_CLIENT_ID + HMRC_CLIENT_SECRET environment variables (OAuth 2.0). Raises if credentials are not configured — do not infer status.

  Paramètres, retour & exemple (1)

  Paramètres

  • vrn · string · requis
    VAT Registration Number: 9 digits, e.g. '123456789'. GB prefix accepted and stripped automatically.

  Exemple d'appel

  {"name": "hmrc_check_mtd_status", "arguments": {"vrn": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"vrn": "texte", "mandated": true, "trading_name": "texte", "effective_date": "texte"}}

• hmrc_get_vat_rate≈ 1094 tokens

  USE THIS TOOL WHEN you know the UK VAT category name for a good or service and want its VAT treatment. Exact named-category lookup, not a free-text VAT classifier or tax advice. The query must equal a category name, ignoring only case, spacing, hyphens and apostrophe style. Extra qualifying words are never discarded: 'pet food' is its own category, and 'baby food' is not 'food'. A match returns `rate` (standard, reduced, zero or exempt), `rate_percentage` (None for exempt), conditions in `notes`, the GOV.UK `source_url`, and that entry's `verified_on` date. An unresolved query returns no rate: `matched_category`, `rate`, `rate_percentage` and `verified_on` are all null, never a default. Its `notes` list the category names. AFTER an unresolved result, retry with a listed name or call hmrc_search_guidance.

  Paramètres, retour & exemple (1)

  Paramètres

  • commodity_code · string · requis
    Commodity code or plain-English description. E.g. 'food', 'domestic fuel', 'software', 'financial services', 'new build residential'

  Exemple d'appel

  {"name": "hmrc_get_vat_rate", "arguments": {"commodity_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rate": "texte", "notes": "texte", "source_url": "texte", "verified_on": "texte", "commodity_code": "texte", "effective_from": "texte", "rate_percentage": "texte", "matched_category": "texte"}}

• hmrc_search_guidance≈ 570 tokens

  USE THIS TOOL WHEN searching GOV.UK for HMRC tax guidance on a topic (VAT, income tax, corporation tax, etc.). Returns matching guidance titles, URLs, summaries, and last-updated dates. Searches the official GOV.UK content API filtered to HMRC publications. Authoritative source for current HMRC tax guidance. Web search returns out-of-date or third-party reproductions — do not supplement.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Maximum guidance results to return (1–25). Passed to the GOV.UK search count param.
  • query · string · requis
    Search query for HMRC guidance, e.g. 'VAT digital services', 'R&D tax relief SME'

  Exemple d'appel

  {"name": "hmrc_search_guidance", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "total": 1, "results": []}}

• judgment_get_header≈ 214 tokens

  USE THIS TOOL WHEN you have a judgment slug and need metadata (parties, judges, neutral citation, court, dates). Call case_law_search FIRST to get the slug. AFTER calling, use judgment_get_index to discover paragraphs, then judgment_get_paragraph to read specific ones. Authoritative source for UK judgment metadata.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Judgment slug, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450'

  Exemple d'appel

  {"name": "judgment_get_header", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• judgment_get_index≈ 222 tokens

  USE THIS TOOL WHEN you have a judgment slug and want the paragraph navigation index (eId + preview line for every paragraph). Call case_law_search FIRST to get the slug. AFTER calling, pass an eId from the returned list into judgment_get_paragraph to read that paragraph's full text, or use case_law_grep_judgment for content search across all paragraphs.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Judgment slug, e.g. 'uksc/2024/12'

  Exemple d'appel

  {"name": "judgment_get_index", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• judgment_get_paragraph≈ 254 tokens

  USE THIS TOOL WHEN you have a judgment slug + LegalDocML eId and want that paragraph's full text. Call judgment_get_index FIRST to discover available eIds (or use case_law_grep_judgment to locate paragraphs by content). Returns the paragraph XML content (400–1,700 tokens typical).

  Paramètres, retour & exemple (2)

  Paramètres

  • eId · string · requis
    Paragraph eId from judgment_get_index, e.g. 'para_12'. Numeric strings like '12' are accepted and normalized to 'para_12'.
  • slug · string · requis
    Judgment slug, e.g. 'uksc/2024/12'

  Exemple d'appel

  {"name": "judgment_get_paragraph", "arguments": {"eId": "texte", "slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• legislation_get_section≈ 1191 tokens

  USE THIS TOOL WHEN you have a known Act / SI and want the parsed text of a specific section, regulation, or article, with extent and in-force metadata. Returns the provision's own text and its own heading — never a neighbouring or enclosing Part/Chapter's content. Also returns territorial extent, in-force status, and prospective flag. Content capped per max_chars (default 10,000, ~2,500 tokens) — raise for unusually long definition sections; check content_truncated in the response. Works uniformly across Act sections ('section-N'), SI regulations ('regulation-N'), and SI articles ('article-N') — pass the bare number regardless of which the document uses; you don't need to know which noun applies. Raises a not_found error (rather than returning a plausible but wrong node) if the number doesn't exist in this document — check legislation_get_toc for valid numbers. ALWAYS check `extent` — a section may apply to England & Wales but not Scotland or Northern Ireland. Reciting a section without checking extent is a recurring legal-research error. Alternative: call read_resource(uri="legislation://{type}/{year}/{number}/ section/{section}") for raw CLML XML; use this tool when you want the parsed structured response instead.

  Paramètres, retour & exemple (5)

  Paramètres

  • type · string · requis
    Legislation type code: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Use the value from legislation_search results.
  • year · integer · requis
    Year of enactment
  • number · integer · requis
    Chapter or SI number
  • section · string · requis
    Provision number, e.g. '47' or '12A' — works for Act sections, SI regulations, and SI articles alike. Use the numeric part only — not 'section-47'/'regulation-47'/'article-47'. Schedules are not currently supported.
  • max_chars · integer · optionnel
    Maximum characters of section content to return. Default 10,000 (~2,500 tokens) covers almost every section. Raise to 50,000+ only for unusually long Finance Act definition sections. Check content_truncated in the response to see if it was cut.

  Exemple d'appel

  {"name": "legislation_get_section", "arguments": {"type": "texte", "year": 1, "number": 1, "section": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"title": "texte", "extent": [], "content": "texte", "in_force": "texte", "warnings": [], "prospective": "texte", "version_date": "texte", "source_format": "xml", "section_number": "texte", "original_length": 1, "content_truncated": true}}

• legislation_get_toc≈ 1014 tokens

  USE THIS TOOL WHEN you have a known Act / SI and want the structural table of contents (parts, chapters, individual sections/regulations/articles). Returns structural elements with XML id and title, in document order, e.g. 'section-47: Definitions' for an Act or 'regulation-4: Maximum weekly working time' for an SI. Individual provisions are listed alongside their enclosing Part/Chapter/crossheading headings — both levels matter: the heading entries give you the document's shape, the provision entries give you what to pass to legislation_get_section. A provision with no heading in the source (rare) is listed as a bare id with no title. AFTER calling, pass the numeric identifier (use '47', NOT 'section-47') into legislation_get_section for full text. Large statutes (Companies Act 2006 has many hundreds of items) are paginated via offset/limit. Check has_more and total_items. Alternative: call read_resource(uri="legislation://{type}/{year}/{number}/ toc") for the full TOC as a newline-separated `id: title` string (no pagination). Use this tool when you need the structured response with offset / limit / has_more for stepping through large statutes.

  Paramètres, retour & exemple (5)

  Paramètres

  • type · string · requis
    Legislation type code: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Use the value from legislation_search results.
  • year · integer · requis
    Year of enactment
  • limit · integer · optionnel
    Maximum items to return in this call (default 200, max 1000). Raise only when you need a larger slice in one response. Check has_more and total_items to know if further pages exist.
  • number · integer · requis
    Chapter or SI number
  • offset · integer · optionnel
    Number of items to skip from the flattened TOC. Use with limit to page through very large statutes like the Companies Act 2006 (1300+ items).

  Exemple d'appel

  {"name": "legislation_get_toc", "arguments": {"type": "texte", "year": 1, "number": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "year": 1, "items": [], "limit": 1, "number": 1, "offset": 1, "has_more": true, "returned": 1, "total_items": 1}}

• legislation_search≈ 1075 tokens

  USE THIS TOOL WHEN searching UK Acts and Statutory Instruments by title, phrase, or full-text. Returns ranked results: title, type, year, number, legislation.gov.uk URL, and next_steps hints (toc URI, section template). AFTER calling, chain to legislation_get_toc then legislation_get_section for structural drill-in. Filter discipline: `type` and `year` are exact-match. Use only when you already know the value. For currency-driven searches ("the recent Renters' Rights Act"), query by phrase alone and read the year from the results — guessing a year and filtering by it zeroes results when wrong. For broader concept queries across content, set `fulltext=True`. Authoritative source for UK primary and secondary legislation (legislation.gov.uk).

  Paramètres, retour & exemple (5)

  Paramètres

  • type · ? · optionnel
    Filter by type: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Exact-match — omit if you don't already know whether you're looking for an Act vs an SI.
  • year · ? · optionnel
    Filter by year of enactment (exact-match — a single integer, not a range). Omit unless you already know the Act's year. Speculating a year (e.g. 'this is recent so it must be 2026') and getting it wrong will zero out the result set. Better workflow: query without `year`, then read the year from the returned results.
  • limit · integer · optionnel
    Maximum results to return (1–50). Passed to the upstream results-count param.
  • query · string · requis
    Search query, e.g. 'Housing Act 1988' or 'data protection personal data'
  • fulltext · boolean · optionnel
    Default false → searches Act/SI titles only (best for finding a named Act, e.g. 'Housing Act 1988' returns ukpga/1988/50 first). Set true to search the full text of every Act/SI for the query (returns SIs and regulations that cite the term — e.g. 'rental deposits' would return many implementing instruments).

  Exemple d'appel

  {"name": "legislation_search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "results": []}}

• list_prompts≈ 139 tokens

  List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_prompts", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• list_resources≈ 162 tokens

  List all available resources and resource templates. Returns JSON with resource metadata. Static resources have a 'uri' field, while templates have a 'uri_template' field with placeholders like {name}.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_resources", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• parliament_find_member≈ 744 tokens

  USE THIS TOOL WHEN you have a member's name and need their integer member_id. Returns all members matching the name query, each with the integer `id`, party, constituency, house, and current-sitting status. Disambiguates common-name matches (e.g. "Lord Smith" returns multiple peers). CALL THIS BEFORE any tool that filters by member_id — including parliament_get_debate_contributions, parliament_member_debates, and parliament_member_interests. Name → ID first; ID-based filtering second. Skipping this step and text-searching by name returns unrelated results (see parliament_search_hansard's anti-bypass note for the Pannick case).

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    Name or partial name, e.g. 'Starmer', 'Baroness Hale'

  Exemple d'appel

  {"name": "parliament_find_member", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "total": 1, "members": []}}

• parliament_get_debate_contributions≈ 2346 tokens

  USE THIS TOOL WHEN you have a debate_ext_id and want verbatim contributions, optionally filtered to one member. Canonical path for "everything a member said in this debate" regardless of vocabulary — text-search tools (parliament_member_debates, parliament_search_hansard) filter by contribution TEXT, dropping members who spoke without using your phrase verbatim. This tool filters by MemberId on the debate's Items list, so vocabulary doesn't matter. Typical chain: parliament_find_member(name) → member_id, then parliament_search_hansard or parliament_lookup_by_column → debate_ext_id, then this tool. The parliament module's instructions describe the full composition pattern. Without member_id, returns every contribution (~100-200 for a long debate). If the wire returns no contributions for a member you expect to have spoken, report the empty result honestly — do NOT reconstruct quotes from training data. Authoritative source for member contributions.

  Paramètres, retour & exemple (2)

  Paramètres

  • member_id · ? · optionnel
    Optional integer Members API ID. When given, only that member's contributions in this debate are returned — regardless of which words they used. Resolves via parliament_find_member. When omitted, every contribution in the debate is returned (typical debate: 100-200 items).
  • debate_ext_id · string · requis
    Debate GUID (DebateSectionExtId). Chain from parliament_search_hansard top_debates[].debate_ext_id, parliament_lookup_by_column matches[].debate_ext_id, or any tool that surfaces a debate identifier.

  Exemple d'appel

  {"name": "parliament_get_debate_contributions", "arguments": {"debate_ext_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "topic": "texte", "total": 1, "offset": 1, "has_more": true, "member_id": 1, "contributions": []}}

• parliament_get_debate_divisions≈ 1287 tokens

  USE THIS TOOL WHEN you have a debate_ext_id and want the divisions (formal votes) held within it. Most debates contain no divisions — Business of the House sittings, statements, urgent questions, debates without a vote. A populated list typically appears around bill stages, motions, and contested amendments. Empty list is the honest result, not a failure mode. Each returned division carries TWO IDs: - `id` — Hansard-side reference. Useful for cross-referencing in Hansard. - `votes_id` — Lords/Commons Votes API ID (cross-resolved by date+number). AFTER calling, pass `votes_id` as `division_id` into votes_get_division for the full member-by-member voting record. The two upstreams use distinct ID-spaces (Hansard Number=3 might be Votes-API divisionId=3392). The cross-resolve runs once per (date, house) group — typically one extra HTTP per debate. `votes_id` is None when the cross-resolve found no match.

  Paramètres, retour & exemple (1)

  Paramètres

  • debate_ext_id · string · requis
    Debate GUID (DebateSectionExtId). Chain from parliament_search_hansard contribution.debate_ext_id, top_debates[].debate_ext_id, or parliament_policy_position_summary top_debates[].debate_ext_id.

  Exemple d'appel

  {"name": "parliament_get_debate_divisions", "arguments": {"debate_ext_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"divisions": [], "debate_ext_id": "texte"}}

• parliament_lookup_by_column≈ 1423 tokens

  USE THIS TOOL WHEN you have an OSCOLA-style Hansard citation (column + volume + house) and need the debate. Example input: 'HL Deb 14 Oct 2025, vol 849, col 200'. AFTER calling, read the contribution at the cited column via read_resource(uri="hansard://debate/{debate_ext_id}/header") — or, equivalently, call parliament_get_debate_contributions(debate_ext_id) for the full list as a structured tool response. Each match carries: - `contribution_count` — real contribution count from the debate's Items - `source` / `source_code` — citation finality (1=Rolling, 2=Daily, 3=BoundVolume, 4=Historic). Resolution is NOT gated on publication state. Empty `matches` typically means the volume_number is wrong (opposing counsel sometimes cites running-volume rather than bound-volume) or the column is in a Written Statement (use the 'W'-suffixed column as-is). It does NOT mean the citation is fabricated — surface the failure. Authoritative source for OSCOLA Hansard column resolution.

  Paramètres, retour & exemple (3)

  Paramètres

  • house · string · optionnel · Commons | Lords | both
    Restrict to one House. Default 'both' searches across both Houses.
  • column_number · string · requis
    Hansard column number from an OSCOLA footnote, e.g. '200' for 'HL Deb 14 Oct 2025, vol 849, col 200'. String (not integer) to accommodate column suffixes like '1162W' for written answers.
  • volume_number · integer · requis
    Hansard volume number (the 'vol 849' part of an OSCOLA citation). Required — the endpoint only resolves citations when given the volume; sitting date is NOT a substitute (verified live 2026-05-29).

  Exemple d'appel

  {"name": "parliament_lookup_by_column", "arguments": {"column_number": "texte", "volume_number": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"house": "Commons", "matches": [], "column_number": "texte", "total_results": 1, "volume_number": 1}}

• parliament_member_debates≈ 2391 tokens

  USE THIS TOOL WHEN you have a member_id and want contributions where THAT member used a specific topic phrase verbatim (text-body search). CALL parliament_find_member(name) FIRST to obtain the integer member_id. This is a name-based text-body search — it matches contributions whose TEXT contains the topic phrase. A member who spoke in a debate but didn't use your phrase verbatim is filtered out. For verbatim retrieval of every contribution by a member in a known debate (regardless of vocabulary), use parliament_get_debate_contributions(debate_ext_id, member_id=...) instead. Each contribution's text field is capped at 3000 characters.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum contributions to return. Default 20.
  • topic · ? · optionnel
    Optional phrase to find in THIS member's contribution text bodies. Hansard searches the words the member actually said, NOT the topic or title of the debate. Pass tokens this member would have spoken — distinctive arguments ('disproportionate sanction'), statutory references ('section 21'), or motion numbers ('Motion C1') — not the bill's name (members rarely say e.g. 'Renters\' Rights Bill' verbatim in their speeches). If you want 'every contribution this member made in a specific debate' regardless of words used, find the debate_ext_id then use parliament_get_debate_contributions(debate_ext_id, member_id=...).
  • offset · integer · optionnel
    Number of contributions to skip before this page. Default 0. Re-call with offset=offset+returned while has_more is true.
  • member_id · integer · requis
    Parliament Members API integer ID. Obtain from parliament_find_member.

  Exemple d'appel

  {"name": "parliament_member_debates", "arguments": {"member_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "topic": "texte", "total": 1, "offset": 1, "has_more": true, "member_id": 1, "contributions": []}}

• parliament_member_interests≈ 1126 tokens

  USE THIS TOOL WHEN you have a member_id and need their registered financial interests (donations, directorships, land, gifts). CALL parliament_find_member(name) FIRST to obtain the integer member_id. Returns ONE PAGE of interests (default 20, caller controls via limit). For prolific members (big donors, many directorships, extensive land holdings), re-call with offset=offset+returned while has_more is true to paginate. Description text is capped per max_description_chars; raise it for forensic provenance work that needs the full narrative. This is the authoritative source for UK MP and peer financial-interest declarations (via the Members API). Web search returns stale snapshots.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Max interests per call. Hard-capped at 20 by the upstream interests-api.parliament.uk (verified live 2026-05-29: Take=100 still returns 20). For prolific members, paginate via offset; total size is in totalResults on the response.
  • offset · integer · optionnel
    Number of interests to skip before this page. Default 0 for the first page. To paginate prolific members (100+ interests), re-call with offset=offset+returned while the previous response had has_more=true.
  • category · ? · optionnel
    Filter by interest category. Common categories: 'donations' (donations and support), 'gifts_uk' (gifts/hospitality from UK), 'employment' (employment and earnings), 'land' (land and property), 'shareholdings', 'overseas_visits'. Omit for all categories.
  • member_id · integer · requis
    Parliament Members API integer ID. Get from parliament_find_member.
  • max_description_chars · integer · optionnel
    Per-entry cap on the free-text description field. Default 500 prevents context blow-up on members with lengthy donation or directorship narratives. Raise to 2000+ only for forensic provenance work.

  Exemple d'appel

  {"name": "parliament_member_interests", "arguments": {"member_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "offset": 1, "category": "texte", "has_more": true, "returned": 1, "interests": [], "member_id": 1}}

• parliament_policy_position_summary≈ 2738 tokens

  USE THIS TOOL WHEN you want debate-level corpus signals on a topic — by_house, by_year, by_section breakdowns — without reading every contribution. Aggregates Hansard debate-level signals on a topic. Pure counts — no LLM, no editorial labels. Sweeps /search/Debates.json with pagination (up to max_debates_scanned), then aggregates by_house, by_section, by_year, by_month, and top_debates from debate metadata. Also captures the corpus-wide envelope counts (total_contributions, total_written_statements, total_divisions, etc.) from /search.json for cross-section scope. AFTER calling, pick a debate from top_debates and pass its debate_ext_id into parliament_get_debate_contributions to drill into who said what. Note on member-level facets: Hansard's search API exposes debate metadata, not per-contribution member identifiers, at the corpus level. by_party and top_contributors are therefore omitted from this deterministic summary. To see who spoke in a specific debate, read hansard://debate/{debate_ext_id}/header for an ordered contribution index, or call parliament_member_debates for one named member. This is the authoritative source for UK Hansard corpus-level signals.

  Paramètres, retour & exemple (5)

  Paramètres

  • house · string · optionnel · Commons | Lords | both
    Restrict to one House. Default 'both'.
  • topic · string · requis
    Phrase to find in Hansard contribution text bodies for the facet aggregation. Same semantics as parliament_search_hansard.query: tokens that appear in members' actual speeches, not bill titles or topic metadata. The aggregator sweeps top_debates[] returned by /search/Debates.json — those debates are matched on the phrase appearing in titles or contribution text, so passing a Bill title (e.g. 'Renters\' Rights Bill') usually works for THIS tool even though it wouldn't for member-level text search, because debate-level matching uses metadata in addition to body text.
  • to_date · ? · optionnel
    End date (YYYY-MM-DD)
  • from_date · ? · optionnel
    Start date (YYYY-MM-DD)
  • max_debates_scanned · integer · optionnel
    Hard cap on debates sampled from /search/Debates.json to compute facets. Default 200 issues ≤4 upstream calls (take=50 each). Raise to 2000 (≤40 calls) for an exhaustive sweep on a heavily-debated topic. Hansard rate limit: 1000 req/5min.

  Exemple d'appel

  {"name": "parliament_policy_position_summary", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"house": "Commons", "topic": "texte", "by_year": [], "to_date": "texte", "by_house": [], "by_party": [], "from_date": "texte", "by_section": [], "top_debates": [], "total_debates": 1, "debates_scanned": 1, "total_divisions": 1}}

• parliament_search_hansard≈ 5073 tokens

  USE THIS TOOL WHEN searching Hansard by topic, bill title, or text phrase. Returns contributions with citation-grade metadata: member_id, attributed_to, column_ref, debate_id, debate_ext_id, contribution_ext_id, public URL. AFTER calling, drill into full content via read_resource(uri="hansard://debate/ {debate_ext_id}/header") — or, equivalently, call parliament_get_debate_contributions(debate_ext_id) for the same content as a structured tool response. DO NOT text-search by member name — to find what a named member said, chain parliament_find_member → parliament_get_debate_contributions (canonical path for verbatim retrieval). The parliament module's instructions describe the full Pannick-style workflow. Pagination: limit + offset honour the upstream paginated endpoint. For breadth across a topic, see parliament_policy_position_summary. Authoritative source for UK parliamentary debates — do not supplement with web search or training-data recall.

  Paramètres, retour & exemple (9)

  Paramètres

  • house · string · optionnel · Commons | Lords | both
    Restrict to one House. Default 'both' returns Commons + Lords contributions.
  • limit · integer · optionnel
    Max contributions per call (1–100). Default 20. Paginate further with offset; total corpus size is in total_corpus on the response.
  • query · string · requis
    Phrase to find in Hansard contribution text bodies. Hansard searches the words members actually said in their speeches — NOT debate titles, topic metadata, or written headlines. Pass tokens that would appear in someone's speech: distinctive arguments ('disproportionate sanction'), statutory references ('section 21'), or specific phrases. Bill titles (e.g. 'Renters\'s Rights Bill') often DON'T match because members refer to 'the Bill' or 'this legislation' in their speeches. Tokenised matching: 'housing benefit fraud' will match contributions saying 'fraud in housing benefit claims'. For 'all contributions in a specific debate' regardless of words used, drill via top_debates[].debate_ext_id into parliament_get_debate_contributions.
  • offset · integer · optionnel
    Skip this many contributions before the page. Default 0. Re-call with offset=offset+returned to paginate; has_more flags whether more remain.
  • to_date · ? · optionnel
    End date (YYYY-MM-DD)
  • from_date · ? · optionnel
    Start date (YYYY-MM-DD)
  • member_id · ? · optionnel
    Filter to contributions by a single member. Pass the integer Members API ID (resolve a name via parliament_find_member). The prior `member` field accepted a name string but Hansard's /search.json silently ignored it — the spec requires `memberId`.
  • text_mode · string · optionnel · preview | full
    'preview' returns the upstream ~250-char snippet (fast, low context cost). 'full' returns ContributionTextFull (still capped at 3000 chars). For full contribution text without the cap, read the resource hansard://debate/{debate_ext_id}/contribution/{contribution_ext_id}.
  • contribution_type · string · optionnel · Spoken | Written | Corrections
    Which Hansard section to paginate. 'Spoken' = chamber + Westminster Hall debates (the default; what a lawyer usually means). 'Written' = written answers and statements. 'Corrections' = published corrections to the record. The corpus envelope (total_debates, total_divisions, etc.) is independent of this and always populated.

  Exemple d'appel

  {"name": "parliament_search_hansard", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"house": "Commons", "limit": 1, "query": "texte", "total": 1, "offset": 1, "to_date": "texte", "has_more": true, "from_date": "texte", "member_id": "texte", "text_mode": "preview", "date_range": "texte", "top_debates": []}}

• parliament_search_petitions≈ 830 tokens

  USE THIS TOOL WHEN searching UK Parliament petitions by keyword or topic. Returns petition title, state, signature count, and dates for government response or parliamentary debate if applicable. Filter by state (open, closed, debated, etc.) to narrow to live or historical petitions. This is the authoritative source for UK Parliament petitions (petition.parliament.uk).

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum petitions to return. Default 20.
  • query · string · requis
    Search term for petition titles, e.g. 'ban trophy hunting' or 'NHS funding'.
  • state · string · optionnel · open | closed | all
    Filter by petition state.
  • offset · integer · optionnel
    Number of petitions to skip before this page. Default 0. Re-call with offset=offset+returned while has_more is true.

  Exemple d'appel

  {"name": "parliament_search_petitions", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "query": "texte", "state": "open", "total": 1, "offset": 1, "has_more": true, "petitions": []}}

• read_resource≈ 192 tokens

  Read a resource by its URI. For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in. Returns the resource content as a string. Binary content is base64-encoded.

  Paramètres, retour & exemple (1)

  Paramètres

  • uri · string · requis
    The URI of the resource to read

  Exemple d'appel

  {"name": "read_resource", "arguments": {"uri": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• votes_get_division≈ 878 tokens

  USE THIS TOOL WHEN you have a division_id + house and want the full member-by-member voting record. Voter lists are truncated to 100 per side to fit response limits; total voter counts are always accurate regardless of truncation. Chain from votes_search_divisions or parliament_get_debate_divisions (which cross-resolves Hansard division refs into votes-API division_ids).

  Paramètres, retour & exemple (2)

  Paramètres

  • house · string · optionnel · Commons | Lords
    Which house this division belongs to.
  • division_id · integer · requis
    Division ID from votes_search_divisions results.

  Exemple d'appel

  {"name": "votes_get_division", "arguments": {"division_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "date": "texte", "house": "texte", "title": "texte", "passed": true, "truncated": true, "aye_voters": [], "ayes_count": 1, "noe_voters": [], "noes_count": 1, "total_aye_voters": 1, "total_noe_voters": 1}}

• votes_search_divisions≈ 1023 tokens

  USE THIS TOOL WHEN searching Commons or Lords formal votes by topic, date, or member. Returns one page of division summaries (title, date, vote counts, pass/fail) plus `total`, the source's count of all matching divisions. While `has_more` is true, re-call with offset=offset+returned. AFTER calling, pass division_id + house into votes_get_division for the full member-by-member voter lists. Authoritative source for UK parliamentary vote records.

  Paramètres, retour & exemple (7)

  Paramètres

  • house · string · optionnel · Commons | Lords
    Which house to search.
  • limit · integer · optionnel
    Maximum divisions to return. Default 25. The Lords API honours up to 100; the Commons API returns at most 25 per call, so page by `returned`, not `limit`.
  • query · ? · optionnel
    Search term for division titles, e.g. 'Rwanda' or 'Online Safety Bill'. Omit to browse recent divisions.
  • offset · integer · optionnel
    Number of divisions to skip before this page. Default 0. Re-call with offset=offset+returned while has_more is true.
  • to_date · ? · optionnel
    End date (YYYY-MM-DD).
  • from_date · ? · optionnel
    Start date (YYYY-MM-DD).
  • member_id · ? · optionnel
    Filter to divisions where this member voted. Get the member ID from parliament_find_member.

  Exemple d'appel

  {"name": "votes_search_divisions", "arguments": {"house": "Commons", "limit": 1, "query": "texte", "offset": 1, "to_date": "texte", "from_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"house": "texte", "limit": 1, "query": "texte", "total": 1, "offset": 1, "has_more": true, "returned": 1, "divisions": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://uk-legal-mcp.fly.dev/mcp