Skip to main content
Glama
Sign In
cfr-free

cfr-free

by deffenda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browse the CFR structure

browse_title38
Read-onlyIdempotent

Navigate Title 38 CFR hierarchy (chapter, part, subpart, subject group) to list available sections and discover valid identifiers before searching.

Instructions

Navigate the Title 38 hierarchy (title → chapter → part → subpart → subject group) and list what exists at a level. With no arguments, returns the chapters. Use this to discover valid parts/subparts before searching. Most sections live inside a subject group: pass the subject_group identifier you saw in a previous response to list the sections it holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_title38"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNopart number, e.g. "4"
chapterNochapter identifier, e.g. "I"
subpartNosubpart letter, e.g. "B" (requires part)
subject_groupNosubject-group identifier, e.g. "ECFRd158704dcab040e" (requires part)

Output Schema

NameRequiredDescriptionDefault
nodeYes
pathYes
childrenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • addedInput schema / properties / subject_group
      Added value: +{
+  "description": "subject-group identifier, e.g. \"ECFRd158704dcab040e\" (requires part)",
+  "maxLength": 40,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add workflow context — which it does by disclosing the no-args default return and the fact that section listing requires an identifier obtained from a prior response. It doesn't discuss result size, pagination, or ordering, so it isn't exhaustive.

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?

Three sentences, front-loaded with the hierarchy shape, then the default behavior, then the workflow hint. No filler and every sentence carries information an agent needs.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still covers default behavior and the call chain for each level. The only omissions are pagination/volume expectations for large listings, which matters mildly for a browse tool with four optional filters.

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

Parameters4/5

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

Schema coverage is 100% with examples for each param, so the baseline is 3; the description adds genuine meaning on top by explaining the hierarchy ordering and that subject_group identifiers come from a previous response rather than being constructed by the agent. That prerequisite is not derivable from the schema.

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 — 'Navigate the Title 38 hierarchy (title → chapter → part → subpart → subject group) and list what exists at a level' — and enumerates the exact levels, so an agent knows precisely what the tool returns. It also implies the boundary versus search_regulations ('before searching') and get_section, which is enough to separate it from siblings.

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?

Explicitly says when to use it ('to discover valid parts/subparts before searching') and describes the no-argument default ('returns the chapters'). The chained-call guidance ('pass the subject_group identifier you saw in a previous response') tells the agent the prerequisite for deeper levels. It stops short of naming specific alternative tools by name, which keeps it at 4.

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