Skip to main content
Glama

Blend Get

blend_get
Read-only

Retrieve a saved blend definition with its queries, joins, and reference paths to inspect or reuse its structure without executing live queries.

Instructions

Read one full saved data-view definition, queries, joins and reference paths.

Preserves opaque server fields. Input/join paths are relative to the returned definition, reference paths are absolute within reportConfig. No live-query execution or datasource/report asset operation is performed.

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": {
      "blend_id": "<blend_id>"
    },
    "name": "blend_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
blend_idYes
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.4/5.0
Behavior4/5

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

With only readOnlyHint=true supplied, the description adds genuinely useful behavior: opaque server fields are preserved (round-trip safe), input/join paths are relative while reference paths are absolute within reportConfig, and the call performs no live query or datasource/report asset operations. These are exactly the traits an agent would otherwise have to guess at, though nothing is said about failure behavior when the blend_id does not exist.

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 the action and payload, then the round-trip and path conventions, then the scope exclusion — a sensible ordering with no filler. The path-semantics sentence is dense and slightly jargon-heavy, but it earns its place for a tool returning reference paths.

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

Completeness3/5

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

An output schema exists and readOnlyHint is set, so return values and safety need no elaboration, and the description covers payload fidelity and path conventions well. The meaningful gap is parameter meaning: for a tool whose sole required input is an opaque blend identifier, saying nothing about it leaves the agent dependent on external context.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, and the description never mentions blend_id or report_id at all — the required identifier's meaning and the optional, nullable report_id's scoping effect are left entirely unexplained. The only hint is a passing reference to "reportConfig" as a path namespace, which does not clarify the parameter.

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?

Specific verb and resource: "Read one full saved data-view definition, queries, joins and reference paths" tells an agent exactly what is fetched and that it is the complete payload rather than a summary. It implicitly distinguishes itself from the listing/creation siblings (blends_list, blend_create) by emphasizing "one full saved" definition, though it never names them.

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 implied rather than stated: an agent can infer this is the retrieval tool for an existing blend, but no alternative is named and no precondition (e.g. needing a known blend_id, or choosing between report-scoped and unscoped reads) is given. The closing negative scope statement ("No live-query execution or datasource/report asset operation is performed") sets boundaries but functions more as behavior than as routing guidance.

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

Deploy Server

Other Tools