Skip to main content
Glama

getAsset

Fetch the full detail of one asset in your organization's own inventory by asset_uuid, returning core's object unchanged. A merged UUID resolves: the response then carries requested_uuid, merged_from, current and source_records. Find asset_uuid values with listAssets. For an asset's products, packages, vulnerabilities, lookup by identifier, and timelines, use queryApi (/v1/assets/{asset_uuid}/products, /packages, /vulnerabilities, /v1/assets/by-identifier).

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": {
      "asset_uuid": "<asset_uuid>"
    },
    "name": "getAsset"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_uuidYesAsset UUID; a merged UUID resolves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses that a merged UUID resolves and that the response then carries requested_uuid, merged_from, current, and source_records, and that core's object is returned unchanged. Gaps remain on non-merged response shape and error behavior for an unknown UUID, and nothing is said about permissions or rate limits, so it falls short of a 5.

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?

Three sentences, front-loaded with the purpose, then the merged-UUID behavior, then sibling routing. The endpoint paths in the final sentence are dense but functional; a slightly tighter phrasing of the queryApi list would make it a 5.

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 one-parameter read with no output schema, the description covers purpose, resolution edge case, response fields in that case, key discovery, and alternatives. It leaves out the ordinary (non-merged) response structure and the failure case for a stale or unknown UUID.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3; the description adds genuine meaning by stating that the single asset_uuid parameter accepts a merged UUID and how that resolution surfaces in the response. It stops short of format examples or error semantics for the parameter.

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 ("Fetch the full detail of one asset"), scopes it ("your organization's own inventory"), and names the key (asset_uuid). It also explicitly distinguishes itself from listAssets and queryApi, so an agent can route correctly without opening a schema.

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?

Gives explicit when-to-use guidance for both directions: use listAssets to obtain asset_uuid values, and use queryApi (with the concrete endpoint paths) for products, packages, vulnerabilities, identifier lookup, and timelines. The boundary against the closest siblings is stated, not inferred.

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