Daystruct

acquire_daystruct_package

Idempotent

Acquire access to an inspected reusable source package at its exact discovered version and digest. With an API key: honors the explicit credit ceiling and key spending limit; repeating acquisition returns the same receipt; then use read_daystruct_package. Without a key, where x402 is enabled: returns x402 PaymentRequired (MCP transport); retry with _meta["x402/payment"] to pay in USDC and receive the artifact. This is not provider task execution or proof of successful integration.

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": {
      "reference": "<reference>",
      "version": "<version>",
      "digest": "<digest>"
    },
    "name": "acquire_daystruct_package"
  }
}

Input Schema

Name	Required	Description	Default
`digest`	Yes
`version`	Yes
`reference`	Yes
`maxPriceCredits`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond annotations: credit ceiling and spending-limit behavior, idempotent receipt return, x402 PaymentRequired retry with _meta payment and USDC, and artifact delivery. These details align with the readOnly false, idempotent true, openWorld true, and destructive false annotations.

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-loads the purpose and then moves through API-key and x402 paths plus exclusions. The semicolon-heavy phrasing is dense, but each sentence carries useful information.

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

Completeness3/5

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

Covers the core acquisition behavior and payment/authentication flow for a complex tool. However, with no output schema and 0% schema descriptions, reference semantics and receipt or artifact return details remain under-explained for reliable invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only partially explains version, digest, and a credit ceiling. It never explains reference or the meaning of maxPriceCredits defaulting to 0, leaving key parameter semantics undocumented.

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, exact version and digest, and explicitly distinguishes acquisition from read_daystruct_package and provider task execution. An agent can identify the acquisition step without opening the schema.

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?

Explains the API-key path and keyless x402 path, gives the follow-up read step, and says this is not task execution or proof of integration. It does not compare against every sibling such as resolve_daystruct_bundle, but the main usage decision is covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Daystruct tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?