Skip to main content
Glama

List Media Contract Termination Actions

media_money_terminations
Read-onlyIdempotent

List the termination and cancellation actions FPDS records on the news publisher and wire families' and the information companies' contracts in the Media Money Register, optionally filtered by family (a substring of a family name), agency (a substring of the agency or department as FPDS prints it, or a short form such as DHS, DoD, HHS or State) and window (before: the 645 days to January 19, 2025; since: January 20, 2025 to the as-of date); at most 25 rows, the most recently signed at the top, with the full count and the counts by window. Each row gives the family, the agency and department, the award and modification numbers, the date signed, FPDS's reason code and its description as printed (F, terminate for convenience; N, legal contract cancellation; E, terminate for default; X, terminate for cause), the amount the action itself records, any initiative code as printed and the product code. Actions are unique by agency, award and modification; a termination of a prepaid subscription can record little or nothing, and the amount is never compared with any claim. Each figure is named in its record's own words: contract obligations (a subscription is a purchase order, delivery order or definitive contract), grant obligations by assistance listing, Treasury account obligations, termination actions with FPDS's reason code as printed, and the laws' own text; fiscal year 2026 is as reported through the as-of date, as Defense Department contract records reach USAspending about 90 days late. Every answer carries the register's question note: these records show federal award and account obligations and the agencies' own termination records; they do not show what any outlet published, why an award was made or ended, or whether any payment affected coverage. Every answer also carries the side-by-side caption, the as-of date, each file's date, the source page on morvs.ai and the licence. Institutions only: no official, consultant, journalist, treasurer or candidate is named; withheld recipients and the advertising firms whose name is a person's full name appear only as counts. No party label is given and no outlet's content is characterised.

Input Schema

NameRequiredDescriptionDefault
agencyNoOptional agency or department name substring as FPDS prints it, or a short form such as DHS, DoD, HHS or State; at most 80 characters.
familyNoOptional case-insensitive substring of a news publisher, wire or information-company family name, for example Politico; at most 80 characters.
windowNoOptional window: before (the 645 days to January 19, 2025) or since (January 20, 2025 to the as-of date); both when omitted, never added.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description adds genuinely useful behavior: a 25-row cap, most-recent-first ordering, full and by-window counts, exact row fields, uniqueness by agency/award/modification, caveats about small prepaid amounts, the 90-day Defense contract lag, and standard disclaimers and redactions carried on every answer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a dense, run-on wall of text with long parentheticals and repeated framing sentences ('Every answer carries...'). It is front-loaded with the purpose, but the volume of policy and disclaimer text far exceeds what is needed to select and invoke the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description is thorough: it describes the row fields, counts, ordering, caps, and the question note/caption/as-of metadata returned with each answer. An agent knows what it will get and how to interpret it.

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 the schema already documents every parameter. The description restates the same filter meanings (agency short forms, family substring, before/since windows) but adds little syntax or interpretation beyond what the schema provides.

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 states a specific verb and resource: it lists termination and cancellation actions FPDS records on media families' contracts in the Media Money Register. That is clear and unique, but it never names or distinguishes itself from close siblings such as media_money_summary, media_money_family or media_money_advertising.

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?

It explains the optional filters and defines the two windows, so usage is implied, but it gives no explicit guidance on when to choose this tool over a sibling like media_money_summary or media_money_family, and no exclusions.

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