Skip to main content
Glama

Stratalize Intelligence

Get Data Freshness Attestation

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.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds real behavior beyond them: the attestation is post-quantum signed, the versions returned are the same ones bound into screening responses, and each call costs $1.00 USDC. Only rate limits, auth requirements, and the exact shape of the signed payload are left unstated.

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?

Three dense sentences with no filler: trigger, return payload, input domain, and price. Usage is front-loaded and each sentence adds distinct information, though the 'Input dataset:' fragment is telegraphic compared with the rest.

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?

With no output schema, the description appropriately names the returned fields (list_version, as-of metadata) and explains their significance to screening. It is nearly complete for a one-parameter read tool, but leaves ambiguous whether the 'signed attestation' itself is returned or only the metadata describing it.

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?

The single parameter has 0% schema description coverage and no enum, so the description must carry the load — and it does, enumerating the accepted values as ofac, oig, or sam. It does not clarify case sensitivity or the exact string form, which is the remaining 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: retrieve a signed attestation of screening-list currency, returning list_version and as-of metadata. The scope is narrowed to synced OFAC, OIG LEIE, and SAM exclusion datasets, which makes the tool unmistakable against the unrelated sibling catalog.

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 explicit triggering context — 'when an examiner or compliance workflow needs' an attestation — which tells the agent the condition that selects this tool. It stops short of naming when-not cases or alternative tools (e.g., the screening call itself), so guidance is clear but not exhaustive.

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