Skip to main content
Glama
1102tools-dev

ecfr-mcp

by 1102tools-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_cfr_content

Read-only

Retrieves full CFR text for a section, subpart, part, or appendix, returning clean parsed content or raw XML with paging for long replies.

Instructions

Get the full text of a CFR section, subpart, part, or appendix.

Returns parsed clean text by default: heading, paragraphs and citations, plus tables, notes, examples, images, pending_amendments and editorial_notes when present. Tables, notes and examples are numbered, and a marker like "[See table 1: ...]" sits in the paragraphs where each appears. [fn N] marks a footnote reference. pending_amendments means eCFR links a published amendment that may not be in effect yet. A subpart, part or appendix request returns one object per section under 'sections', each with its own section number and heading. Set raw_xml=True to get the original XML instead.

Answers longer than about 60,000 characters come in pages: the reply says page and total_pages, and page=2 (and so on) returns the rest.

Specify the narrowest scope possible to keep responses manageable:

  • section='15.305' for a single FAR section

  • subpart='15.3' for a subpart

  • part='15' for an entire part (can be large)

  • chapter='1' for an entire chapter (often >1 MB, avoid)

  • appendix='Appendix A to Chapter 2' (with chapter='2') for a DFARS appendix

Date auto-resolves to the latest available if not provided. Do NOT use today's date directly -- eCFR lags 1-2 business days and today often 404s.

Title 48 = FAR/DFARS. Chapter 1 = FAR (Parts 1-99), Chapter 2 = DFARS (Parts 200-299). Other chapters = agency FAR supplements (GSAR, VAAR, HSAR, etc.).

For DFARS clauses, use chapter='2' (e.g., section='252.227-7014').

part/subpart/section accept int or string. Common prefix mistakes like section='FAR 15.305' or '48 CFR 15.305' are stripped automatically, and trailing paragraph cites like section='15.305(a)(2)' resolve to the base section '15.305'.

Input Schema

NameRequiredDescriptionDefault
dateNo
pageNo
partNo
chapterNo
raw_xmlNo
sectionNo
subpartNo
appendixNo
title_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.33
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "title": "Page",
+  "type": "integer"
+}
  2. Changed5 schema fields changedv1.0.7
    • addedInput schema / properties / appendix
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Appendix"
+}
    • addedInput schema / properties / chapter / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / part / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / section / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / subpart / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
  3. First observedv0.2.6

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: parsed clean text structure, numbered tables/notes/examples, inline markers, pending_amendments semantics, pagination over ~60k characters, and raw_xml output. These details materially help an agent understand what will be returned and how to handle large responses.

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-loads the purpose and return behavior, then moves into scope selection and parameter conventions. It is long, but the length is mostly justified by the 9-parameter schema and pagination/date complexity; a few details could be tightened.

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?

Even with an output schema present, the description adds critical context for correct invocation: eCFR date lag, FAR/DFARS chapter mapping, appendix usage, pagination, and scope selection. Nothing essential for selecting parameters or interpreting responses appears missing.

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 thoroughly. It explains section/subpart/part/chapter/appendix scoping, date auto-resolution caveats, page handling, raw_xml, title_number defaults, and even prefix/paragraph-cite normalization.

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 and resource: 'Get the full text of a CFR section, subpart, part, or appendix.' It clearly distinguishes full-text retrieval from search/navigation siblings by naming the exact scope forms it supports.

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 strong operational guidance: choose the narrowest scope, avoid chapter-level requests, resolve dates automatically, and use chapter='2' for DFARS. It does not explicitly name when to use search_cfr or get_cfr_structure instead, so it falls short of full alternative-routing guidance.

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

Deploy Server

Other Tools