Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Get Data Freshness

get_data_freshness
Read-onlyIdempotent

Assess whether data is still fresh, undated or conflicting. use it rather than create_signed_data_snapshot for freshness, not signed data snapshot; an object with 58 fields including Accept, User-Agent. $0.02 USDC.

Input Schema

NameRequiredDescriptionDefault
as_ofNoThe date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
claimsNoThe claims to evaluate, as a list of {subject, predicate, object} or as free text.
source_urlNoThe source url this operation operates on. See the schema for its type and whether it is required.
budget_secondsNoThe budget seconds this operation operates on. See the schema for its type and whether it is required.
reference_timeNoThe reference time this operation operates on. See the schema for its type and whether it is required.

Output Schema

NameRequiredDescriptionDefault
aNoThe `a` field of the response.
bNoThe `b` field of the response.
gapNoThe `gap` field of the response.
keyNoThe `key` field of the response.
urlNoThe `url` field of the response.
whyNoThe `why` field of the response.
asOfNoThe `asOf` field of the response.
dateNoThe `date` field of the response.
etagNoThe `etag` field of the response.
kindNoThe `kind` field of the response.
noteNoA note on how the answer was produced.
ruleNoThe rule or criteria that decided the verdict.
as_ofNoThe date the answer is computed as of.
errorNoThe machine-readable error code, when the operation failed.
AcceptNoThe `Accept` field of the response.
detailYesHuman-readable explanation of the verdict.
errorsNoThe `errors` field of the response.
key_idNoThe `key_id` field of the response.
methodNoThe `method` field of the response.
sha256NoThe `sha256` field of the response.
statusNoThe status of the operation.
isStaleNoThe `isStale` field of the response.
verdictYesThe decision this tool returned.
is_staleNoThe `is_stale` field of the response.
signedByNoThe `signedBy` field of the response.
algorithmNoThe `algorithm` field of the response.
conflictsNoThe `conflicts` field of the response.
signatureYesThe Ed25519 signature over the evidence core, base64-encoded.
sourceUrlNoThe `sourceUrl` field of the response.
User-AgentNoThe `User-Agent` field of the response.
ageSecondsNoThe `ageSeconds` field of the response.
ed25519SigNoThe `ed25519Sig` field of the response.
source_urlNoThe `source_url` field of the response.
age_secondsNoThe `age_seconds` field of the response.
content_typeNoThe `content_type` field of the response.
coverageGapsNoThe `coverageGaps` field of the response.
evidenceCoreNoThe `evidenceCore` field of the response.
observedHttpNoThe `observedHttp` field of the response.
publicKeyHexNoThe `publicKeyHex` field of the response.
rulesVersionNoVersion of the rules evaluated.
budgetSecondsNoThe `budgetSeconds` field of the response.
coverage_gapsNoThe `coverage_gaps` field of the response.
last_modifiedNoThe `last_modified` field of the response.
observed_httpNoThe `observed_http` field of the response.
output_sha256YesSHA-256 hex digest of the canonical evidence core.
referenceTimeNoThe `referenceTime` field of the response.
rules_versionNoThe `rules_version` field of the response.
a_source_indexNoThe `a_source_index` field of the response.
asOfAssumedUtcNoThe `asOfAssumedUtc` field of the response.
b_source_indexNoThe `b_source_index` field of the response.
budget_secondsNoThe `budget_seconds` field of the response.
profileVersionNoVersion of the answer profile.
reference_timeNoThe `reference_time` field of the response.
canonicalSha256NoThe `canonicalSha256` field of the response.
reproducibilityNoThe `reproducibility` field of the response.
as_of_assumed_utcNoThe `as_of_assumed_utc` field of the response.
referenceTimeSourceNoThe `referenceTimeSource` field of the response.
reference_time_sourceNoThe `reference_time_source` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed59 schema fields changed
    • addedOutput schema / properties / Accept
      Added value: +{
      +  "description": "The `Accept` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / User-Agent
      Added value: +{
      +  "description": "The `User-Agent` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / a
      Added value: +{
      +  "description": "The `a` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / a_source_index
      Added value: +{
      +  "description": "The `a_source_index` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / ageSeconds
      Added value: +{
      +  "description": "The `ageSeconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / age_seconds
      Added value: +{
      +  "description": "The `age_seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / algorithm
      Added value: +{
      +  "description": "The `algorithm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / asOf
      Added value: +{
      +  "description": "The `asOf` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / asOfAssumedUtc
      Added value: +{
      +  "description": "The `asOfAssumedUtc` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / as_of
      Added value: +{
      +  "description": "The date the answer is computed as of.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / as_of_assumed_utc
      Added value: +{
      +  "description": "The `as_of_assumed_utc` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / b
      Added value: +{
      +  "description": "The `b` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / b_source_index
      Added value: +{
      +  "description": "The `b_source_index` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / budgetSeconds
      Added value: +{
      +  "description": "The `budgetSeconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / budget_seconds
      Added value: +{
      +  "description": "The `budget_seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalSha256
      Added value: +{
      +  "description": "The `canonicalSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / conflicts
      Added value: +{
      +  "description": "The `conflicts` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / content_type
      Added value: +{
      +  "description": "The `content_type` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverageGaps
      Added value: +{
      +  "description": "The `coverageGaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage_gaps
      Added value: +{
      +  "description": "The `coverage_gaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / date
      Added value: +{
      +  "description": "The `date` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / detail
      Added value: +{
      +  "description": "Human-readable explanation of the verdict.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / ed25519Sig
      Added value: +{
      +  "description": "The `ed25519Sig` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "description": "The machine-readable error code, when the operation failed.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / errors
      Added value: +{
      +  "description": "The `errors` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / etag
      Added value: +{
      +  "description": "The `etag` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidenceCore
      Added value: +{
      +  "description": "The `evidenceCore` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / gap
      Added value: +{
      +  "description": "The `gap` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / isStale
      Added value: +{
      +  "description": "The `isStale` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / is_stale
      Added value: +{
      +  "description": "The `is_stale` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / key
      Added value: +{
      +  "description": "The `key` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / key_id
      Added value: +{
      +  "description": "The `key_id` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / kind
      Added value: +{
      +  "description": "The `kind` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / last_modified
      Added value: +{
      +  "description": "The `last_modified` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / method
      Added value: +{
      +  "description": "The `method` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "A note on how the answer was produced.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / observedHttp
      Added value: +{
      +  "description": "The `observedHttp` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / observed_http
      Added value: +{
      +  "description": "The `observed_http` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / output_sha256
      Added value: +{
      +  "description": "SHA-256 hex digest of the canonical evidence core.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / profileVersion
      Added value: +{
      +  "description": "Version of the answer profile.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / publicKeyHex
      Added value: +{
      +  "description": "The `publicKeyHex` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / referenceTime
      Added value: +{
      +  "description": "The `referenceTime` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / referenceTimeSource
      Added value: +{
      +  "description": "The `referenceTimeSource` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reference_time
      Added value: +{
      +  "description": "The `reference_time` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reference_time_source
      Added value: +{
      +  "description": "The `reference_time_source` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reproducibility
      Added value: +{
      +  "description": "The `reproducibility` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / rule
      Added value: +{
      +  "description": "The rule or criteria that decided the verdict.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / rulesVersion
      Added value: +{
      +  "description": "Version of the rules evaluated.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / rules_version
      Added value: +{
      +  "description": "The `rules_version` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sha256
      Added value: +{
      +  "description": "The `sha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signature
      Added value: +{
      +  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / signedBy
      Added value: +{
      +  "description": "The `signedBy` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sourceUrl
      Added value: +{
      +  "description": "The `sourceUrl` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "description": "The `source_url` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / status / description
      Added value: +"The status of the operation."
    • addedOutput schema / properties / url
      Added value: +{
      +  "description": "The `url` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "description": "The decision this tool returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / why
      Added value: +{
      +  "description": "The `why` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "detail",
      +  "output_sha256",
      +  "signature",
      +  "verdict"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description does add one piece of context annotations cannot carry — the $0.02 USDC price, which matters for an agent deciding whether to spend. The '58 fields including Accept, User-Agent' sentence implies HTTP-header detail that is noise and doesn't clarify behavior.

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

Conciseness3/5

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

It is short and the purpose leads, which is good. However the middle sentence ('an object with 58 fields including Accept, User-Agent') earns no place — it is leaked implementation detail, and the semicolon/run-on splice between the alternative clause and that fragment hurts parseability.

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 an output schema present, return values need no explanation, and all five parameters are covered by the schema. Purpose, cost and one routing alternative are all given, so an agent has enough to call it correctly; only the relationship to the near-twin verify_data_freshness is missing.

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 description coverage is 100% with all five parameters documented, so the baseline is 3. The description contributes nothing parameter-specific — it never explains what `claims`, `reference_time` or `budget_seconds` actually control in a freshness judgment.

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?

"Assess whether data is still fresh, undated or conflicting" gives a concrete verb and an evaluative outcome, which distinguishes it from most siblings. It also explicitly contrasts with create_signed_data_snapshot, though the near-identical sibling verify_data_freshness goes unmentioned, leaving the sharpest ambiguity unresolved.

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 names one alternative (create_signed_data_snapshot) and gives the condition selecting this tool for freshness, which is genuine routing guidance. But it never says when NOT to use it, and the closest competing tool (verify_data_freshness, plus resolve_data_conflict for the 'conflicting' case) is never mentioned, so the agent must still guess between near-duplicates.

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.