CueFrame

Resolve Builtin Component

resolve_builtin_component

Read-onlyIdempotent

Resolve a selected builtin component-library card using its exact collection, id and revision. Returns the canonical pinned document and source snapshots for a preset or recipe, or the exact source for a definition. Preserve documentSha256 and all identities; a missing revision refuses without falling back to another version or scope. Resolve before apply_template; do not invent wrapper source or reconstruct a package from a thumbnail.

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": {
      "collection": "<collection>",
      "id": "<id>",
      "revision": "<revision>"
    },
    "name": "resolve_builtin_component"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`revision`	Yes
`collection`	Yes

Output Schema

Name	Required	Description	Default
`card`	No
`preset`	No
`source`	No
`sources`	No
`document`	No
`documentText`	No
`previewMedia`	No
`documentSha256`	No
`previewDelivery`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 31, 2026

addedOutput schema / properties / previewDelivery

Added value: +{
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "byteLength": {
+          "exclusiveMinimum": 0,
+          "maximum": 9007199254740991,
+          "type": "integer"
+        },
+        "mimeType": {
+          "type": "string"
+        },
+        "sha256": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "status": {
+          "const": "delivered",
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "sha256",
+        "mimeType",
+        "byteLength"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "reason": {
+          "type": "string"
+        },
+        "status": {
+          "const": "unavailable",
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "reason"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "actualSha256": {
+          "type": "string"
+        },
+        "expectedSha256": {
+          "type": "string"
+        },
+        "status": {
+          "const": "hash_mismatch",
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "expectedSha256",
+        "actualSha256"
+      ],
+      "type": "object"
+    }
+  ]
+}

addedOutput schema / properties / previewMedia

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / required
```
Added value: +[
+  "previewDelivery"
+]
```

First observedOct 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior beyond them: it returns the canonical pinned document plus source snapshots, requires preserving documentSha256 and all identities, and fails closed on a missing revision without falling back to another version or scope. That fail-closed guarantee is exactly the kind of non-obvious behavior an agent must know before calling.

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?

Four sentences, front-loaded with purpose and return shape, then constraints, then ordering. Every sentence carries information, though the final clause about thumbnails is slightly cryptic and the density makes it a tight read rather than an effortless one.

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?

Return values are largely covered by the existing output schema and the description reinforces the key invariant (documentSha256, identities), and the fail-closed revision behavior is spelled out. The remaining gap is discovery: nothing tells the agent how to find a valid collection/id/revision in the first place, which matters for a tool that refuses rather than falls back.

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 description coverage is 0%, so the description must carry the load, and it does name all three parameters and stresses that revision must be exact with no version fallback. It does not explain what a 'collection' is, how to obtain valid collection/id values, or that revision is a 64-char hex digest (left to the schema pattern), so the compensation is good but not complete.

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 ('resolve'), a specific resource ('builtin component-library card'), and the exact keying (collection, id, revision). It also distinguishes what is returned for a preset/recipe versus a definition, and implicitly separates itself from thumbnail/preview siblings with 'do not reconstruct a package from a thumbnail'.

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?

'Resolve before apply_template' gives an explicit ordering constraint, and 'do not invent wrapper source or reconstruct a package from a thumbnail' tells the agent when not to substitute guesswork or a preview sibling. It stops short of naming the adjacent read tools (get_component_source, preview_card, search_registry_items) as explicit alternatives, so the routing is implied rather than fully enumerated.

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

All CueFrame 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.