Skip to main content
Glama

Numonic

by ai.numonic
OverviewDiscussionsAdmin

GetAssetDetails

Retrieve comprehensive details for a specific asset by its SHA-1 hash, including how it was made. Answers 'which prompt, model and workflow produced this?' directly — no download needed: prompts.positive/prompts.negative hold the prompt, models[] lists every model the workflow loaded (name, type such as checkpoint/unet/lora/vae, loader node_id), workflow.workflow_json is the full ComfyUI graph (with workflow.tool_name, node_count, custom_nodes), and generation_parameters holds sampler settings (model_name, seed, steps, cfg_scale, sampler, scheduler) when they were read from a standard KSampler node, else null (the graph still has them). provenance.lineage_source says where that lineage came from: 'extracted' (read by Numonic from the stored file; prompts.source/workflow.source are then 'extracted'), 'client_asserted' (only the uploader's claim), or 'unknown' (nothing asserted or found). provenance.asserted_parameters holds the uploader's own claim about the generator, model and settings (StoreAsset prompt_metadata.parameters_used, e.g. {generator: 'fal', model: 'fal-ai/flux/schnell'}), or null; it is client-asserted and never merged into generation_parameters. Also returns title, description, tags, collections, provenance (creation prompt, parent assets), embedding info and copyright. For Model Library records of those models (base model, trigger words, usage) call GetAssetModels. Optionally generates a short download link for the original file (valid 5 minutes; fetch it with a tool such as curl or fetch rather than retyping it), and optionally returns a small inline preview image (include_image) so the asset can be seen without fetching a URL. For a URL that does not expire, approve the asset and call PublishAsset.

Input Schema

NameRequiredDescriptionDefault
asset_hYesThe Asset Hash (SHA-1) of the asset to retrieve
tenant_idNoOptional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected.
include_imageNoIf true, also returns a small preview of the asset as an MCP image content block (JPEG/WebP ingest thumbnail, no embedded metadata, max 200 KB), for clients that cannot fetch URLs. preview_image in the result reports whether it was included. Defaults to false.
include_download_urlNoIf true, includes a download link for the original asset binary, valid 5 minutes. Fetch it with a tool (curl, fetch) rather than retyping it; a mistyped or expired link returns an error saying to request a new one. Defaults to false.
include_raw_metadataNoIf true, also returns the raw extractor output (extracted_metadata) and the node-by-node workflow_graph. These can be tens of kilobytes; the default response already carries prompts, models and workflow.workflow_json. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tenant_id / description
      Previous value: -"UUID of the tenant"New value: +"Optional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected."
    • changedInput schema / required
      Previous value: -[
-  "tenant_id",
-  "asset_h"
-]New value: +[
+  "asset_h"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / include_download_url / description
      Previous value: -"If true, includes a short-lived signed URL for downloading the original asset binary. Defaults to false."New value: +"If true, includes a download link for the original asset binary, valid 5 minutes. Fetch it with a tool (curl, fetch) rather than retyping it; a mistyped or expired link returns an error saying to request a new one. Defaults to false."
  3. Changed1 schema field changed
    • addedInput schema / properties / include_image
      Added value: +{
+  "default": false,
+  "description": "If true, also returns a small preview of the asset as an MCP image content block (JPEG/WebP ingest thumbnail, no embedded metadata, max 200 KB), for clients that cannot fetch URLs. preview_image in the result reports whether it was included. Defaults to false.",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that generation_parameters may be null, that provenance.lineage_source takes 'extracted'/'client_asserted'/'unknown', that asserted_parameters are never merged, and that the download link is valid only 5 minutes. It stops short of explicitly stating side-effect/read-only status or auth requirements beyond the tenant note, so not a full 5 for an annotation-free tool.

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-loaded with purpose and the return-value map, then organized by field path, which makes it scannable despite its length. It is dense and does repeat some schema content (download-link expiry, curl/fetch), but nearly every clause carries field-level semantics an agent needs given there is no output schema.

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

Completeness5/5

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

There is no output schema and no annotations, so the description must document the return payload — and it does, enumerating prompts, models[], workflow.workflow_json, generation_parameters, provenance.lineage_source/asserted_parameters, plus title, tags, collections, embedding and copyright. Nothing an agent needs to interpret the response or pick the right sibling 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% and each parameter already has a thorough description, so baseline is 3. The description restates rather than adds: the 5-minute link validity and the curl/fetch guidance are already in the schema text for include_download_url, and include_image's rationale largely duplicates its schema description.

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?

Opens with a specific verb+resource and a precise selector: 'Retrieve comprehensive details for a specific asset by its SHA-1 hash, including how it was made.' It even frames the question it answers ('which prompt, model and workflow produced this?'), which instantly separates it from GetAssetPublicUrl and PublishAsset, and it names GetAssetModels for the adjacent but distinct need.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: 'For Model Library records of those models ... call GetAssetModels' and 'For a URL that does not expire, approve the asset and call PublishAsset.' It also states when to reach for the optional flags (include_image for clients that cannot fetch URLs, include_download_url for a short-lived link), so the agent knows both when to use this tool and when a sibling is better.

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

All Numonic toolsInspect
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