Skip to main content
Glama

Search the FAR and DFARS

search_far
Read-onlyIdempotent

Search the FAR and the DFARS (48 CFR chapters 1 and 2, as codified in the eCFR): sections whose title or text has every word, or a section number (e.g. 52.219-14) straight to it. reg: FAR | DFARS to limit. Returns section numbers, titles and a snippet; read one with get_far_section. The codified text lags the Revolutionary FAR Overhaul's class deviations.

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": {
      "query": "<query>"
    },
    "name": "search_far"
  }
}

Input Schema

NameRequiredDescriptionDefault
regNoLimit to one regulation: FAR or DFARS; omit for both.
queryYesWords that must all appear in the section's title or text (e.g. "limitations on subcontracting"), or a section number (e.g. "52.219-14").

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": "search_farDictOutput",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond them: it discloses the return shape (section numbers, titles, snippet) and a caveat that codified text lags the Revolutionary FAR Overhaul class deviations, which affects result trustworthiness.

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 core purpose and keeps to a few dense sentences with no filler. The telegraphic phrasing ('reg: FAR | DFARS to limit') is slightly clipped but still readable and efficient.

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 two-parameter read-only search with an output schema, the description covers purpose, return shape, follow-up tool, and a data-freshness caveat. Only minor gaps remain, such as result ordering or pagination behavior.

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%, so both parameters are already documented, including the reg enum and the query format. The description restates the same examples (52.219-14, reg: FAR | DFARS) without adding syntax or matching semantics beyond the schema, so baseline 3 applies.

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 (search FAR/DFARS sections by title/text or section number) and scopes it to 48 CFR chapters 1-2 in the eCFR. It also distinguishes itself from get_far_section by noting that search returns snippets while that tool reads a full section.

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 clear context for use (keyword or section-number lookup, optional reg filter) and explicitly routes the agent to get_far_section to read a result. It does not state when not to use it or how it differs from other search_* siblings, but the primary alternative is named.

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