Skip to main content
Glama

Fox River Press

Look up a federal credit deadline

credit_deadlines
Read-onlyIdempotent

Federal deadlines in U.S. consumer credit (disputes, debt validation, freezes, fraud alerts, reporting periods), each with the statute or rule that sets it and the guide that explains it. Filter by a word or phrase.

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

Input Schema

NameRequiredDescriptionDefault
queryNoA word or phrase to match, for example dispute, freeze, collector or bankruptcy. Omit for every deadline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds modestly useful behavioral context by saying each result is accompanied by its governing statute and an explanatory guide, but says nothing about result volume, ordering, or whether matching is substring vs exact — relevant for an idempotent read that could return everything when the filter is omitted.

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?

Two tight sentences, front-loaded with the resource and its scope before the filtering mechanics; nothing is padded. The closing sentence marginally duplicates the schema's parameter description, which is the only waste.

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 single-optional-parameter, read-only lookup with a fully covered schema, complete annotations, no output schema and no nesting, the description gives enough to select and invoke it correctly. Only the exact matching behavior and result-size expectations are unaddressed, both minor here.

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 parameter already documents itself with examples ('dispute, freeze, collector or bankruptcy') and the omit-for-everything behavior. The description's 'Filter by a word or phrase' largely restates that, adding no matching semantics (case sensitivity, multi-word handling) beyond the schema — baseline 3 is appropriate.

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 a specific resource (federal deadlines in U.S. consumer credit) and enumerates its scope (disputes, debt validation, freezes, fraud alerts, reporting periods), plus what each entry carries (the statute/rule and the explaining guide). It is unmistakably distinct from the unrelated siblings (chargers, court records, datasets), though it never names 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is a reference lookup and that the query narrows results, with the schema stating 'Omit for every deadline.' There is no explicit when-to-use vs when-not guidance, no framing of common scenarios (e.g. 'use before advising on a dispute window'), and no alternatives to weigh against.

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