Skip to main content
Glama

federal-regulations-mcp-server

regulations_get_cfr_section

regulations_get_cfr_section
Read-onlyIdempotent

Read the codified text at a CFR location via eCFR — current or as of a past date. Answers "what does 40 CFR 50.1 say today?" and "...as of 2019-01-01?". Three locations: title + part + section for one section; title + part alone for the whole part, with its Authority and Source notes, an index of its sections, and the names of its appendices; title + appendix for one appendix, passing the identifier exactly as regulations_browse_cfr emits it. A section can be written as people cite it — "61", "§ 141.61", "141.61(c)", or the full cite "40 CFR 141.61" in part 141 all read 40 CFR 141.61 — and a part as "Part 141"; the response names the identifier it read. Text comes back as a window of up to 64,000 characters (max_chars raises it to 200,000) with the total length and, when text remains, the offset to resume from; whole parts run to millions of characters, so page with offset or read a single section. eCFR retains historical versions from 2017 through the title's up-to-date date; a date outside that window is rejected with the window named. Current single-section reads are served from a synced local mirror when it holds the title's latest eCFR issue; the source is reported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoPoint-in-time date, ISO 8601 (YYYY-MM-DD). Default current. eCFR serves 2017-01-01 through the title's up-to-date date, usually a few days behind today; a date outside that window is rejected, naming the window.
partNoCFR part within the title (e.g. "50"). Parts can be alphanumeric; a leading "Part" or "Pt." is dropped ("Part 141" reads part 141). Required unless appendix is given, where it is optional but recommended: an appendix identifier is unique within a part, not within a title, so without a part eCFR picks one of the matches. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences.
titleYesCFR title number (1–50). E.g. 40 for "Protection of Environment".
offsetNoCharacter offset into the text where the window starts (default 0). Pass bodyTextNextOffset from the previous call to read on, or a sections[].offset from a whole-part read to jump to that section.
sectionNoSection within the part, normally written part.section as eCFR identifies it ("141.61"). Also accepted: the number alone ("61" in part 141), a leading "§" or "Sec.", a paragraph cite ("141.61(c)"), which reads the whole section, and the full cite this tool returns as cfrCite ("40 CFR 141.61", "14 CFR 241 § 25"), whose title has to match title. Identifiers eCFR writes differently are read as given — 14 CFR 241 numbers its sections "25" and "1-1". Omit to fetch the entire part. Cannot be combined with appendix.
appendixNoAppendix identifier, verbatim as eCFR writes it — the `appendix` field or the leading phrase of the `cfrCite` on a regulations_browse_cfr appendix node or search hit. It is free-form prose, not a letter: "Appendix A-1 to Part 50", "Appendix A to Subpart C of Part 4", "Schedule I to Part 789", "Special Federal Aviation Regulation No. 88". Pass the whole phrase; a short form such as "A-1" matches nothing. Cannot be combined with section.
max_charsNoMost text characters to return in this window (1–200,000, default 64,000).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe issue/point-in-time date the text reflects (ISO 8601).
partNoCFR part; null only for an appendix that hangs off a chapter, subchapter, or subtitle rather than a part.
errorNoPresent when the call failed. Absent on success.
notesNoThe part's editorial, general, and OMB control-number notes, in document order; empty when it has none. Present only on a whole-part read.
titleNoCFR title number.
noticeNoHow a part or section written another way was resolved, and guidance when the offset is at or past the end of the text.
sourceNoProvenance: the synced mirror, or the live eCFR API.
cfrCiteNoAssembled cite — "40 CFR 50.1" for a section, "40 CFR 50" for a part, "Appendix A-1 to Part 50, Title 40" for an appendix (eCFR's own form, leading with the identifier this tool takes back as `appendix`).
headingNoSection, part, or appendix heading — for a whole part, the part's own ("PART 141—NATIONAL PRIMARY DRINKING WATER REGULATIONS").
sectionNoSection identifier that was read — the resolved form when the input was written differently ("141.61" for "§ 141.61(c)"); null when a whole part or an appendix was fetched.
appendixNoAppendix identifier; null when a section or whole part was fetched.
bodyTextNoOne window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references ("[Figure: /graphics/…]"), a section's own statutory authority and OMB control-number note, and its trailing source citation are kept in document order; part-, subpart-, and subject-group-level Authority and Source are not (see authority, sourceNote, and sections[]). Superscripts read ^x and subscripts _x, braced where the run would otherwise be ambiguous (3 × 10^−8, SO_2, CO_{2}e); a footnote reference or label reads [n]; diacritics and overlines are Unicode combining marks on their base character (x̄, R̅M̅). The source citation is the bracketed Federal Register history a section ends in ("[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]") — to reach the rulemaking that produced this text, pass one of its cites from 1994 on to regulations_search_rules as citation ("81 FR 68276") with the date printed beside it as citation_date ("2016-10-03"). Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading ("[Reserved]").
sectionsNoPresent only on a whole-part fetch — the part's sections whose text falls in this window, in order, without their text (bodyText carries it). A section that begins before the window and runs into it is included, so its offset can be below bodyTextOffset. Empty when the offset is past the end. To list every section and appendix of a part without reading its text, use regulations_browse_cfr in structure mode with title and part.
authorityNoThe part's Authority — the statutes it is issued under, without the "Authority:" label; null when the part states none. Present only on a whole-part read. A subpart or subject group that states its own carries it on its sections[] entries; a single-section or appendix read carries no part- or subpart-level notes, so read the whole part for them.
appendicesNoPresent on a whole-part fetch when the part has appendices — their identifiers and headings, without their text. A part's appendices routinely run several times the length of its sections, so they are not inlined; call this tool again with `appendix` set to one of these identifiers to read it. Absent means the part has no appendices; a single-section or appendix fetch never carries this field.
sourceNoteNoThe part's Source note — the Federal Register document it was issued in, without the "Source:" label ("40 FR 59570, Dec. 24, 1975, unless otherwise noted."), which holds for every section with no source citation of its own; null when the part states none. Not to be confused with source, which names the corpus that answered. Present only on a whole-part read; subpart and subject-group Source notes ride on sections[] entries.
hierarchyPathNoHuman-readable hierarchy path.
bodyTextLengthNoCharacters in the location's whole text.
bodyTextOffsetNoCharacter offset bodyText starts at.
bodyTextNextOffsetNoOffset to pass as offset to read the next window — present only when text remains past this window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / part / description
      Previous value: -"CFR part within the title (e.g. \"50\"). Parts can be alphanumeric. Required unless appendix is given, where it is optional but recommended: an appendix identifier is unique within a part, not within a title, so without a part eCFR picks one of the matches. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences."New value: +"CFR part within the title (e.g. \"50\"). Parts can be alphanumeric; a leading \"Part\" or \"Pt.\" is dropped (\"Part 141\" reads part 141). Required unless appendix is given, where it is optional but recommended: an appendix identifier is unique within a part, not within a title, so without a part eCFR picks one of the matches. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences."
    • changedInput schema / properties / section / description
      Previous value: -"Section within the part, normally written part.section as eCFR identifies it (\"141.61\"). Also accepted: the number alone (\"61\" in part 141), a leading \"§\" or \"Sec.\", and a paragraph cite (\"141.61(c)\"), which reads the whole section. Identifiers eCFR writes differently are read as given — 14 CFR 241 numbers its sections \"25\" and \"1-1\". Omit to fetch the entire part. Cannot be combined with appendix."New value: +"Section within the part, normally written part.section as eCFR identifies it (\"141.61\"). Also accepted: the number alone (\"61\" in part 141), a leading \"§\" or \"Sec.\", a paragraph cite (\"141.61(c)\"), which reads the whole section, and the full cite this tool returns as cfrCite (\"40 CFR 141.61\", \"14 CFR 241 § 25\"), whose title has to match title. Identifiers eCFR writes differently are read as given — 14 CFR 241 numbers its sections \"25\" and \"1-1\". Omit to fetch the entire part. Cannot be combined with appendix."
    • addedOutput schema / properties / authority
      Added value: +{
      +  "description": "The part's Authority — the statutes it is issued under, without the \"Authority:\" label; null when the part states none. Present only on a whole-part read. A subpart or subject group that states its own carries it on its sections[] entries; a single-section or appendix read carries no part- or subpart-level notes, so read the whole part for them.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / bodyText / description
      Previous value: -"One window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and each section's trailing source citation are kept in document order. The source citation is the bracketed Federal Register history a section ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — to reach the rulemaking that produced this text, pass one of its cites from 1994 on to regulations_search_rules as citation (\"81 FR 68276\") with the date printed beside it as citation_date (\"2016-10-03\"). Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading (\"[Reserved]\")."New value: +"One window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), a section's own statutory authority and OMB control-number note, and its trailing source citation are kept in document order; part-, subpart-, and subject-group-level Authority and Source are not (see authority, sourceNote, and sections[]). Superscripts read ^x and subscripts _x, braced where the run would otherwise be ambiguous (3 × 10^−8, SO_2, CO_{2}e); a footnote reference or label reads [n]; diacritics and overlines are Unicode combining marks on their base character (x̄, R̅M̅). The source citation is the bracketed Federal Register history a section ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — to reach the rulemaking that produced this text, pass one of its cites from 1994 on to regulations_search_rules as citation (\"81 FR 68276\") with the date printed beside it as citation_date (\"2016-10-03\"). Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading (\"[Reserved]\")."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No such title/part/section/appendix at that date, under the section as given or any form it resolves to. `location_required`: Neither part nor appendix was given, so the call names no location to read. `conflicting_target`: Both section and appendix were given. They name two different locations, and picking one silently would return text the call did not ask for. `date_out_of_range`: The requested date precedes eCFR historical coverage (2017-01-01) or is past the title's up-to-date date. `upstream_unavailable`: eCFR returned a 5xx, timed out, or served an HTML error page (live path). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No such title/part/section/appendix at that date, under the section as given or any form it resolves to. `location_required`: Neither part nor appendix was given, so the call names no location to read. `conflicting_target`: Both section and appendix were given. They name two different locations, and picking one silently would return text the call did not ask for. `conflicting_title`: section is written as a full cite (\"21 CFR 141.61\") naming a different title than title. `date_out_of_range`: The requested date precedes eCFR historical coverage (2017-01-01) or is past the title's up-to-date date. `upstream_unavailable`: eCFR returned a 5xx, timed out, or served an HTML error page (live path). Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "not_found",
      -  "location_required",
      -  "conflicting_target",
      -  "date_out_of_range",
      -  "upstream_unavailable"
      -]New value: +[
      +  "not_found",
      +  "location_required",
      +  "conflicting_target",
      +  "conflicting_title",
      +  "date_out_of_range",
      +  "upstream_unavailable"
      +]
    • changedOutput schema / properties / heading / description
      Previous value: -"Section, part, or appendix heading."New value: +"Section, part, or appendix heading — for a whole part, the part's own (\"PART 141—NATIONAL PRIMARY DRINKING WATER REGULATIONS\")."
    • addedOutput schema / properties / notes
      Added value: +{
      +  "description": "The part's editorial, general, and OMB control-number notes, in document order; empty when it has none. Present only on a whole-part read.",
      +  "items": {
      +    "description": "One note, its label dropped.",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"How a section written another way was resolved, and guidance when the offset is at or past the end of the text."New value: +"How a part or section written another way was resolved, and guidance when the offset is at or past the end of the text."
    • addedOutput schema / properties / sections / items / properties / authority
      Added value: +{
      +  "description": "The Authority its subpart or subject group states for this section; absent when the part's authority applies.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sections / items / properties / sourceNote
      Added value: +{
      +  "description": "The Source note its subpart or subject group states for this section; absent when the part's sourceNote applies.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sourceNote
      Added value: +{
      +  "description": "The part's Source note — the Federal Register document it was issued in, without the \"Source:\" label (\"40 FR 59570, Dec. 24, 1975, unless otherwise noted.\"), which holds for every section with no source citation of its own; null when the part states none. Not to be confused with source, which names the corpus that answered. Present only on a whole-part read; subpart and subject-group Source notes ride on sections[] entries.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / bodyText / description
      Previous value: -"One window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and each section's trailing source citation are kept in document order. The source citation is the bracketed Federal Register history a section ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — pass one of its FR cites to regulations_search_rules to reach the rulemaking that produced this text. Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading (\"[Reserved]\")."New value: +"One window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and each section's trailing source citation are kept in document order. The source citation is the bracketed Federal Register history a section ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — to reach the rulemaking that produced this text, pass one of its cites from 1994 on to regulations_search_rules as citation (\"81 FR 68276\") with the date printed beside it as citation_date (\"2016-10-03\"). Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading (\"[Reserved]\")."
  3. Changed19 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Point-in-time date, ISO 8601 (YYYY-MM-DD). Default current. eCFR retains historical versions back to ~2017; a date before coverage is rejected."New value: +"Point-in-time date, ISO 8601 (YYYY-MM-DD). Default current. eCFR serves 2017-01-01 through the title's up-to-date date, usually a few days behind today; a date outside that window is rejected, naming the window."
    • addedInput schema / properties / max_chars
      Added value: +{
      +  "description": "Most text characters to return in this window (1–200,000, default 64,000).",
      +  "maximum": 200000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Character offset into the text where the window starts (default 0). Pass bodyTextNextOffset from the previous call to read on, or a sections[].offset from a whole-part read to jump to that section.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / section / description
      Previous value: -"Section identifier within the part (e.g. \"50.1\"). Omit to fetch the entire part — large parts can be very long; prefer a specific section when you know it. Cannot be combined with appendix."New value: +"Section within the part, normally written part.section as eCFR identifies it (\"141.61\"). Also accepted: the number alone (\"61\" in part 141), a leading \"§\" or \"Sec.\", and a paragraph cite (\"141.61(c)\"), which reads the whole section. Identifiers eCFR writes differently are read as given — 14 CFR 241 numbers its sections \"25\" and \"1-1\". Omit to fetch the entire part. Cannot be combined with appendix."
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "cfrCite",
      -      "title",
      -      "part",
      -      "section",
      -      "appendix",
      -      "heading",
      -      "hierarchyPath",
      -      "date",
      -      "source",
      -      "bodyText"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "cfrCite",
      +      "title",
      +      "part",
      +      "section",
      +      "appendix",
      +      "heading",
      +      "hierarchyPath",
      +      "date",
      +      "source",
      +      "bodyText",
      +      "bodyTextOffset",
      +      "bodyTextLength"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • changedOutput schema / properties / bodyText / description
      Previous value: -"Text of the section, part, or appendix, XML stripped to plain text. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and the trailing source citation are kept in document order. The source citation is the bracketed Federal Register history the text ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — pass one of its FR cites to regulations_search_rules to reach the rulemaking that produced this text. Empty only where the location is a placeholder carrying nothing but its heading — \"[Reserved]\", or an agency variant of it."New value: +"One window of the location's text, starting at bodyTextOffset, XML stripped to plain text. A whole part's text is each section's heading and body in order. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and each section's trailing source citation are kept in document order. The source citation is the bracketed Federal Register history a section ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — pass one of its FR cites to regulations_search_rules to reach the rulemaking that produced this text. Empty when the offset is at or past the end, or where the location is a placeholder carrying nothing but its heading (\"[Reserved]\")."
    • addedOutput schema / properties / bodyTextLength
      Added value: +{
      +  "description": "Characters in the location's whole text.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / bodyTextNextOffset
      Added value: +{
      +  "description": "Offset to pass as offset to read the next window — present only when text remains past this window.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / bodyTextOffset
      Added value: +{
      +  "description": "Character offset bodyText starts at.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No such title/part/section/appendix at that date. `location_required`: Neither part nor appendix was given, so the call names no location to read. `conflicting_target`: Both section and appendix were given. They name two different locations, and picking one silently would return text the call did not ask for. `date_out_of_range`: The requested date precedes eCFR historical coverage. `upstream_unavailable`: eCFR returned a 5xx, timed out, or served an HTML error page (live path). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No such title/part/section/appendix at that date, under the section as given or any form it resolves to. `location_required`: Neither part nor appendix was given, so the call names no location to read. `conflicting_target`: Both section and appendix were given. They name two different locations, and picking one silently would return text the call did not ask for. `date_out_of_range`: The requested date precedes eCFR historical coverage (2017-01-01) or is past the title's up-to-date date. `upstream_unavailable`: eCFR returned a 5xx, timed out, or served an HTML error page (live path). Other values are possible when a failure originates below the handler."
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "How a section written another way was resolved, and guidance when the offset is at or past the end of the text.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / section / description
      Previous value: -"Section identifier; null when a whole part or an appendix was fetched."New value: +"Section identifier that was read — the resolved form when the input was written differently (\"141.61\" for \"§ 141.61(c)\"); null when a whole part or an appendix was fetched."
    • changedOutput schema / properties / sections / description
      Previous value: -"Present only when a whole part was fetched — each section in the part."New value: +"Present only on a whole-part fetch — the part's sections whose text falls in this window, in order, without their text (bodyText carries it). A section that begins before the window and runs into it is included, so its offset can be below bodyTextOffset. Empty when the offset is past the end. To list every section and appendix of a part without reading its text, use regulations_browse_cfr in structure mode with title and part."
    • changedOutput schema / properties / sections / items / description
      Previous value: -"One section within the part."New value: +"One section of the part, without its text."
    • removedOutput schema / properties / sections / items / properties / bodyText
      Removed value: -{
      -  "description": "Section text.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / sections / items / properties / cfrCite
      Added value: +{
      +  "description": "Assembled cite for the section.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sections / items / properties / offset
      Added value: +{
      +  "description": "Offset in the whole part's text where this section starts — pass as offset to read from it.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / sections / items / properties / section / description
      Previous value: -"Section identifier."New value: +"Section identifier — pass as section to read it alone."
    • changedOutput schema / properties / sections / items / required
      Previous value: -[
      -  "section",
      -  "heading",
      -  "bodyText"
      -]New value: +[
      +  "section",
      +  "heading",
      +  "cfrCite",
      +  "offset"
      +]
  4. Changed6 schema fields changed
    • removedOutput schema / properties / appendix / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / appendix / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / part / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / part / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / section / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / section / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  5. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "cfrCite",
      +      "title",
      +      "part",
      +      "section",
      +      "appendix",
      +      "heading",
      +      "hierarchyPath",
      +      "date",
      +      "source",
      +      "bodyText"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: No such title/part/section/appendix at that date. `location_required`: Neither part nor appendix was given, so the call names no location to read. `conflicting_target`: Both section and appendix were given. They name two different locations, and picking one silently would return text the call did not ask for. `date_out_of_range`: The requested date precedes eCFR historical coverage. `upstream_unavailable`: eCFR returned a 5xx, timed out, or served an HTML error page (live path). Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "not_found",
      +            "location_required",
      +            "conflicting_target",
      +            "date_out_of_range",
      +            "upstream_unavailable"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "cfrCite",
      -  "title",
      -  "part",
      -  "section",
      -  "appendix",
      -  "heading",
      -  "hierarchyPath",
      -  "date",
      -  "source",
      -  "bodyText"
      -]
  6. Changed1 schema field changed
    • changedOutput schema / properties / bodyText / description
      Previous value: -"Text of the section, part, or appendix, XML stripped to plain text. Paragraphs, subheadings, editorial notes, and tables (one pipe-delimited line per row) are kept in document order. Empty for a reserved appendix and for one whose whole content is a figure image."New value: +"Text of the section, part, or appendix, XML stripped to plain text. Paragraphs, subheadings, editorial notes, tables (one pipe-delimited line per row), figure references (\"[Figure: /graphics/…]\"), and the trailing source citation are kept in document order. The source citation is the bracketed Federal Register history the text ends in (\"[36 FR 22384, Nov. 25, 1971, as amended at 81 FR 68276, Oct. 3, 2016]\") — pass one of its FR cites to regulations_search_rules to reach the rulemaking that produced this text. Empty only where the location is a placeholder carrying nothing but its heading — \"[Reserved]\", or an agency variant of it."
  7. Changed14 schema fields changed
    • addedInput schema / properties / appendix
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": "",
      +      "type": "string"
      +    },
      +    {
      +      "description": "Appendix identifier (e.g. \"Appendix A-1 to Part 50\").",
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Appendix identifier, verbatim as eCFR writes it — the `appendix` field or the leading phrase of the `cfrCite` on a regulations_browse_cfr appendix node or search hit. It is free-form prose, not a letter: \"Appendix A-1 to Part 50\", \"Appendix A to Subpart C of Part 4\", \"Schedule I to Part 789\", \"Special Federal Aviation Regulation No. 88\". Pass the whole phrase; a short form such as \"A-1\" matches nothing. Cannot be combined with section."
      +}
    • changedInput schema / properties / part / description
      Previous value: -"CFR part within the title (e.g. \"50\"). Parts can be alphanumeric. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences."New value: +"CFR part within the title (e.g. \"50\"). Parts can be alphanumeric. Required unless appendix is given, where it is optional but recommended: an appendix identifier is unique within a part, not within a title, so without a part eCFR picks one of the matches. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences."
    • changedInput schema / properties / section / description
      Previous value: -"Section identifier within the part (e.g. \"50.1\"). Omit to fetch the entire part — large parts can be very long; prefer a specific section when you know it."New value: +"Section identifier within the part (e.g. \"50.1\"). Omit to fetch the entire part — large parts can be very long; prefer a specific section when you know it. Cannot be combined with appendix."
    • changedInput schema / required
      Previous value: -[
      -  "title",
      -  "part"
      -]New value: +[
      +  "title"
      +]
    • addedOutput schema / properties / appendices
      Added value: +{
      +  "description": "Present on a whole-part fetch when the part has appendices — their identifiers and headings, without their text. A part's appendices routinely run several times the length of its sections, so they are not inlined; call this tool again with `appendix` set to one of these identifiers to read it. Absent means the part has no appendices; a single-section or appendix fetch never carries this field.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "One appendix in the part, named but not inlined.",
      +    "properties": {
      +      "appendix": {
      +        "description": "Appendix identifier, for a follow-up read.",
      +        "type": "string"
      +      },
      +      "heading": {
      +        "description": "Appendix heading.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "appendix",
      +      "heading"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / appendix
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Appendix identifier; null when a section or whole part was fetched."
      +}
    • changedOutput schema / properties / bodyText / description
      Previous value: -"Section text, XML stripped to plain text (paragraph structure preserved)."New value: +"Text of the section, part, or appendix, XML stripped to plain text. Paragraphs, subheadings, editorial notes, and tables (one pipe-delimited line per row) are kept in document order. Empty for a reserved appendix and for one whose whole content is a figure image."
    • changedOutput schema / properties / cfrCite / description
      Previous value: -"Assembled cite, e.g. \"40 CFR 50.1\"."New value: +"Assembled cite — \"40 CFR 50.1\" for a section, \"40 CFR 50\" for a part, \"Appendix A-1 to Part 50, Title 40\" for an appendix (eCFR's own form, leading with the identifier this tool takes back as `appendix`)."
    • changedOutput schema / properties / heading / description
      Previous value: -"Section/part heading."New value: +"Section, part, or appendix heading."
    • addedOutput schema / properties / part / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / part / description
      Previous value: -"CFR part."New value: +"CFR part; null only for an appendix that hangs off a chapter, subchapter, or subtitle rather than a part."
    • removedOutput schema / properties / part / type
      Removed value: -"string"
    • changedOutput schema / properties / section / description
      Previous value: -"Section identifier; null when a whole part was fetched."New value: +"Section identifier; null when a whole part or an appendix was fetched."
    • changedOutput schema / required
      Previous value: -[
      -  "cfrCite",
      -  "title",
      -  "part",
      -  "section",
      -  "heading",
      -  "hierarchyPath",
      -  "date",
      -  "source",
      -  "bodyText"
      -]New value: +[
      +  "cfrCite",
      +  "title",
      +  "part",
      +  "section",
      +  "appendix",
      +  "heading",
      +  "hierarchyPath",
      +  "date",
      +  "source",
      +  "bodyText"
      +]
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses pagination behavior (64k default, 200k max, offset to resume), date availability window (2017 to up-to-date), rejection behavior with the window named, and the local mirror serving current single-section reads with source reporting. These add substantial context beyond the readOnly/idempotent annotations, and there is no contradiction.

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?

Though long, the description is information-dense and logically organized: purpose, three location modes, citation flexibility, window/pagination, date bounds, and mirror behavior. Each sentence carries actionable information with no filler, making the length justified for a tool with this complexity.

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?

The description covers all three location modes, explains all seven parameters' behaviors, describes return windowing and error handling, and points to regulations_browse_cfr for identifier discovery. With an output schema present, nothing needed for correct invocation is 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 coverage is 100%, so baseline is 3. The description far exceeds the baseline by explaining accepted section citation formats ('61', '§ 141.61', '141.61(c)'), appendix verbatim matching, offset semantics for paging, and date range constraints. This makes parameter usage much clearer than the schema alone.

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 opening sentence, 'Read the codified text at a CFR location via eCFR — current or as of a past date', is a specific verb+resource statement. The example questions ('what does 40 CFR 50.1 say today?') and the three location modes make the tool's purpose unambiguous and distinct from sibling tools that browse, search, or handle dockets.

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 gives clear context on when to use this tool (reading current or historical CFR text) and how to target sections, parts, or appendices. It references regulations_browse_cfr as the source for identifiers, implicitly distinguishing browsing from reading, but it does not explicitly name alternatives or exclusions. The use case is well-specified, so this is a strong 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.