Skip to main content
Glama

get_def_codes_reference

Read-only

Return all Disaster Emergency Fund (DEFC) codes with public laws.

DEFCs are used to filter awards funded by specific supplemental appropriations (COVID-19, IIJA, IRA, etc.).

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": "get_def_codes_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and openWorld, so the safety profile is covered. The description adds meaningful non-obvious behavior: it returns the full set of codes ('all') together with their public laws, and it defines the domain concept DEFC, which the annotations do not.

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 short, front-loaded sentences with no filler. The primary outcome (all DEFC codes plus public laws) comes first, followed by the one piece of context needed to interpret them.

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 zero-argument reference lookup with an output schema and read-only annotations, the description covers what the tool returns and why DEFCs exist. It is nearly complete, missing only explicit guidance on how this reference relates to the sibling lookup tools that would consume DEFC values.

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?

This tool takes zero parameters, so the baseline is 4. The schema has 100% coverage and no parameter semantics are needed; the description correctly avoids discussing arguments.

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?

States a specific verb and resource ('Return all Disaster Emergency Fund (DEFC) codes with public laws') and explains what DEFCs are. It distinguishes itself by resource from siblings like get_award_types_reference, though it doesn't explicitly name or contrast with any sibling.

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?

The second sentence gives useful context for when DEFC codes matter ('used to filter awards funded by specific supplemental appropriations (COVID-19, IIJA, IRA, etc.)'), implying usage. However, it never states when to call this tool versus related reference tools or what to do with the returned codes, leaving selection to inference.

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.