Skip to main content
Glama

Read a FAR or DFARS section

get_far_section
Read-onlyIdempotent

One FAR or DFARS section's full text (paragraphs), its part and subpart, the sections it refers to and the ones referring to it, and Federal Register rules changing its part. Cite it as FAR (or DFARS) with the as-of date in source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "get_far_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesA FAR or DFARS section number, e.g. "52.204-21", "19.502-2" or "252.204-7012".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "get_far_sectionDictOutput",
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real scope context beyond that — it discloses that cross-references are returned in both directions and that part-level Federal Register rules are included, which tells an agent this call is richer than a plain text fetch. It stops short of noting size/truncation or latency characteristics for what could be a long section.

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?

Two sentences, front-loaded with the resource and its contents, then a short citation rule. Every clause carries distinct information (text, hierarchy, cross-refs, rule changes, citation format) with no filler or repetition of the title.

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?

With one required parameter at full schema coverage, complete annotations, and an output schema handling return values, the description covers everything an agent needs to call it correctly. The only gap is the absence of routing guidance against the search-oriented siblings.

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?

Schema coverage is 100% and the schema already gives format examples ('52.204-21', '19.502-2', '252.204-7012'). The description adds only the framing that DFARS sections are also valid and reiterates the section-number form, which is largely redundant with the schema. Baseline 3 applies since the schema carries the parameter burden.

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 names the exact resource (one FAR or DFARS section) and enumerates the payload: full paragraph text, part/subpart, inbound and outbound cross-references, and Federal Register rules. It is unmistakably a single-section lookup rather than a search, though it never names the sibling search_far to make that contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'One ... section' plus the example section numbers signal that this is a direct lookup by section identifier. There is no statement of when to prefer this over search_far, no prerequisite (e.g., needing an exact section number rather than a topic), and no exclusion conditions. The citation instruction guides output use, not tool selection.

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.

Resources