Skip to main content
Glama

get_data_freshness_attestation

Read-only

Use when an examiner or compliance workflow needs a post-quantum signed attestation of screening-list currency. Returns list_version and as-of metadata for synced OFAC, OIG LEIE, or SAM exclusion datasets — the same versions bound into screening responses. Input dataset: ofac, oig, or sam. $1.00 USDC per call.

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": {
      "dataset": "<dataset>"
    },
    "name": "get_data_freshness_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), and the description adds real context beyond them: the response is cryptographically signed ('post-quantum'), the datasets are synced/versioned, and each call costs $1.00 USDC. The pricing disclosure is exactly the kind of behavioral trait annotations cannot express. It does not describe rate limits, failure modes, or what happens when a dataset is unsynced.

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-loaded with the use condition, followed by return content, valid inputs, and price — a sensible ordering with little slack. The 'same versions bound into screening responses' clause is arguably the only slightly indirect phrasing, but it conveys genuine context, so the text stays efficient.

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 single-parameter, read-only tool with no output schema, the description supplies the trigger condition, the enumerated valid input values, the shape of the return (version and as-of metadata), and the cost. Nothing an agent needs in order to decide to call it and construct the call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema declares only a bare string with no enum, so the description carries the full burden — and it does so by enumerating all three valid values ('ofac, oig, or sam'). That is precisely the information an agent needs to form a valid call, compensating completely for the schema gap.

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 — a signed attestation of screening-list currency — and names the exact datasets covered (OFAC, OIG LEIE, SAM). It also tells the agent what comes back (list_version and as-of metadata) and ties it to the versions bound into screening responses, so there is no confusion with the benchmark-style siblings.

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?

Explicit trigger given: 'Use when an examiner or compliance workflow needs a post-quantum signed attestation of screening-list currency.' That is a clear when-to-use condition tied to a concrete situation. It stops short of naming a when-not-to-use condition or an alternative tool, but no sibling in the catalog appears to be a plausible substitute.

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