Skip to main content
Glama
1102tools-dev

ecfr-mcp

by 1102tools-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_sections_in_part

Read-only

List all sections and headings within a FAR or DFARS part to review its scope before examining specific sections.

Instructions

List all sections in a FAR/DFARS part with their headings.

Returns a flat list of sections extracted from the structure tree. Useful for understanding the scope of a FAR part before drilling into specific sections.

Default chapter='1' (FAR). Use chapter='2' for DFARS.

part_number accepts int or string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
chapterNo1
part_numberYes
title_numberNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.7
    • addedInput schema / properties / chapter / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / part_number / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  }
+]
  2. First observedv0.2.6

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool read-only and non-destructive, so the bar is lower. The description adds that it returns a flat list of sections and clarifies chapter defaults, but it does not disclose details about pagination, error behavior, or open-world data changes.

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

Conciseness5/5

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

The description is succinct and front-loaded. Every sentence earns its place: purpose, output shape, usage hint, and parameter guidance. No filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with an output schema and protective annotations, the description provides enough to call it successfully with part_number and chapter. The main gap is the unexplained 'date' and 'title_number' parameters, though their defaults reduce immediate risk.

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

Parameters3/5

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

With 0% schema description coverage, the description must carry parameter meaning. It explains that chapter='1' is FAR and chapter='2' is DFARS, and that part_number accepts int or string, but date and title_number are left undocumented, requiring agent inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action and resource: 'List all sections in a FAR/DFARS part with their headings.' It adds that the result is a flat list extracted from the structure tree, which helps separate it from sibling tools like get_cfr_structure, though it does not name an alternative explicitly.

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?

It gives clear context for when to use the tool: 'Useful for understanding the scope of a FAR part before drilling into specific sections.' It also explains the chapter parameter for FAR vs DFARS, but does not mention when not to use it or suggest an alternative tool.

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