Skip to main content
Glama

spArxx.io | Zero-Knowledge Blockchain Timestamping

create_timestamp

Compute the SHA-256 hash of the file locally - the file itself is never uploaded, and spArxx.io never stores it. Call this with that hash plus basic file metadata to register a provenance timestamp. This deducts spArks from the account (dynamic cost. Call get_pricing or get_balance first if you want to pre-check spend; a 402 response here means ins...

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesExactly one of file_hash/client_hash and exactly one of file_size/file_size_bytes must be present. These are aliases kept for client compatibility, not two different values.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
statusNo
messageNo
correlation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / body / properties / codename / anyOf
      Added value: +[
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / body / properties / codename / description
      Removed value: -"Optional human-friendly label for the timestamped item."
    • addedInput schema / properties / body / properties / disclose_identity / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / body / properties / disclose_identity / description
      Removed value: -"Per-transaction override for whether this certificate's verify page/API/manifest discloses the account's name and email together, or withholds both. Omit to inherit the account's stored disclose_identity_default preference (defaults to true if never set). Ghost/guest accounts always withhold identity regardless of this value ... there is no toggle for them."
    • addedInput schema / properties / body / properties / mime_type / anyOf
      Added value: +[
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / body / properties / mime_type / description
      Removed value: -"Optional MIME type of the file (e.g., 'audio/wav', 'image/png'), if known. Purely informational, and stored with the evidence record, not independently verified against file content."
    • addedInput schema / properties / body / properties / original_file_name / anyOf
      Added value: +[
      +  {
      +    "maxLength": 255,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / body / properties / original_file_name / description
      Removed value: -"Optional: the file's original name, if different from file_name (e.g., before local renaming). Purely informational, stored with the evidence record."
  2. Changed6 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Exactly one of file_hash/client_hash and exactly one of file_size/file_size_bytes must be present — they are aliases kept for client compatibility, not two different values."New value: +"Exactly one of file_hash/client_hash and exactly one of file_size/file_size_bytes must be present. These are aliases kept for client compatibility, not two different values."
    • changedInput schema / properties / body / properties / disclose_identity / description
      Previous value: -"Whether this certificate's verify page/API/manifest should disclose the account's name and email together, or withhold both. Omit to inherit the account's own disclose_identity_default preference. Ignored for Ghost/unclaimed accounts, which are always anonymous regardless of this value."New value: +"Per-transaction override for whether this certificate's verify page/API/manifest discloses the account's name and email together, or withholds both. Omit to inherit the account's stored disclose_identity_default preference (defaults to true if never set). Ghost/guest accounts always withhold identity regardless of this value ... there is no toggle for them."
    • addedInput schema / properties / body / properties / file_name / description
      Added value: +"The file's name as the caller knows it (e.g., 'final_mix.wav'). Used for display and is included in the receipt kit. Required; not used to derive mime_type or validate the hash."
    • addedInput schema / properties / body / properties / mime_type / description
      Added value: +"Optional MIME type of the file (e.g., 'audio/wav', 'image/png'), if known. Purely informational, and stored with the evidence record, not independently verified against file content."
    • addedInput schema / properties / body / properties / original_file_name / description
      Added value: +"Optional: the file's original name, if different from file_name (e.g., before local renaming). Purely informational, stored with the evidence record."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "correlation_id": {
      +      "type": "string"
      +    },
      +    "data": {
      +      "properties": {
      +        "action": {
      +          "example": "EJECT_REQUIRED",
      +          "type": "string"
      +        },
      +        "cost_deducted": {
      +          "description": "Actual spArks deducted for this call. Dynamic. Driven by the TIMESTAMP_COST env var (default 25), not a fixed 1 spark.",
      +          "type": "integer"
      +        },
      +        "custody_status": {
      +          "example": "self_custody",
      +          "type": "string"
      +        },
      +        "evidence_id": {
      +          "format": "uuid",
      +          "type": "string"
      +        },
      +        "remaining_credits": {
      +          "type": "number"
      +        },
      +        "sparks_remaining": {
      +          "type": "number"
      +        },
      +        "status": {
      +          "example": "pending",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "example": "success",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers: the file is "never uploaded, and spArxx.io never stores it," the tool "deducts spArks from the account" with dynamic cost, and a 402 response signals a spending failure. This is precisely the side-effect and privacy context an agent needs beyond what the schema conveys.

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?

The description is dense and front-loaded: the crucial privacy property and local-hash workflow lead, followed by cost guidance and error semantics. The visible text contains no filler, though it is a single unbroken paragraph and is truncated mid-sentence at "a 402 response here means ins...".

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 mutating, cost-deducting tool with nested alias parameters and no annotations, the description covers the essentials: local workflow, no-upload guarantee, spend pre-check, and a 402 signal. An output schema is present so return values need no explanation, but the truncated sentence leaves 402 semantics incomplete and auth requirements are not addressed.

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%, and the schema already documents each parameter's meaning, constraints, and alias relationships (file_hash/client_hash, file_size/file_size_bytes), including the body-level rule that exactly one of each alias pair must be present. The description adds only workflow framing ("that hash plus basic file metadata") rather than new per-parameter meaning, so the baseline of 3 applies.

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?

The description states a specific verb+resource: "register a provenance timestamp" using a locally-computed hash plus file metadata. It clearly separates the caller's local hash computation from the tool's registration role, and the create_ prefix distinguishes it from the read/verify sibling tools (get_evidence, verify_certificate, list_evidence).

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?

The description explicitly routes to siblings: "Call get_pricing or get_balance first if you want to pre-check spend," giving conditional context for using alternatives. It implies when to use the tool (after computing a local SHA-256 hash) but does not spell out when to prefer verify_certificate or get_evidence instead.

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