Skip to main content
Glama

Renew download links

assets
Read-onlyIdempotent

Use this when a download link was lost or is about to expire, or a render replied rendering: pass the asset ids from the result to get the links or the status, with no re-render and no charge. Files live about 2 h; verify:true re-checks a file's hash. An id that has expired says so: the same request again returns the same files (the synthesizer is deterministic). Schema a964948f.

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": {
      "ids": "<ids>"
    },
    "name": "assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
verifyNoRe-check stored sha256

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
  6. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
  7. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
  8. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
  11. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
  14. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
  15. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description still adds real value: 2 h file lifetime, no charge, expired-id behavior, and determinism guaranteeing identical files on retry. It does not describe the response shape or the no-charge boundary in more detail.

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?

Trigger condition is appropriately front-loaded, but the middle sentences are dense and hard to parse, and the trailing 'Schema a964948f' tag duplicates the schema and adds nothing.

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 two-parameter, no-output-schema tool with annotations present, the definition covers when to call, what it returns (links or status), link lifetime, and retry behavior. Missing only return-field detail that an output schema would otherwise supply.

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 coverage is 50%, so the description partly compensates: it clarifies ids come from a result and that verify re-checks the file hash. However it omits the 1–16 item bounds and the exact meaning of the returned status field, leaving some schema detail unexpanded.

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?

States a concrete outcome: pass asset ids to get download links or status without re-rendering. The 'no re-render' clause distinguishes it from the render sibling, though the tool name 'assets' is generic and the sentence is somewhat tangled.

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 triggers: a link was lost, is about to expire, or a render replied 'rendering'. It implicitly excludes the render path via 'no re-render', but names no alternatives outright and provides no when-not guidance.

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