Webanto

Read a managed image source reference

webanto_get_asset

Read-onlyIdempotent

Reload an exact-version managed image reference through its current organization-owned parent. Missing, inactive, moved or stale images are refused. Returns metadata and a native review link, never image bytes, credentials or external-reuse approval. No provider request, generation, publication or credit cost.

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": {
      "ref": "<ref>"
    },
    "name": "webanto_get_asset"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	Exact typed source reference, including parent, image identifier and version, from list_assets.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that the description adds real value: which reference states are rejected (missing, inactive, moved, stale), what is returned (metadata plus a native review link) and what is explicitly not returned (image bytes, credentials, external-reuse approval), plus the absence of side effects or credit cost.

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

Conciseness5/5

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

Four short sentences, front-loaded with the operation and scope, then constraints, then return contract, then cost profile. Every sentence carries distinct information; nothing restates the name or the annotations.

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 a full output schema and rich annotations, the description covers the refusal cases, return scope and side-effect profile, which is enough to call the tool correctly. The one gap is recovery guidance for a refused or stale reference (e.g. re-list via list_assets), which would complete the loop.

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 100% and the nested oneOf variants, parent IDs and version pattern are thoroughly documented in the schema itself. The description reinforces the exact-version/staleness semantics but contributes no syntax or format detail beyond what the schema already gives, so the baseline 3 applies.

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?

The description names a specific verb and resource: reload an exact-version managed image reference scoped to its current organization-owned parent. That is far more precise than the title alone and implicitly separates it from the enumeration sibling list_assets, though the routing hint ('from list_assets') appears only in the schema, not the description.

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?

Usage is only implied: the 'exact-version' framing and 'stale images are refused' tell the agent this is a point-fetch of a previously listed reference, but the description never states when to choose it over list_assets or the other get_* siblings, nor what to do when a reference is refused.

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

All Webanto 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?