Skip to main content
Glama

Blends List

blends_list
Read-only

Lists report-local data views with inputs, joins, filter IDs, and exact references, including single-query views, and flags missing sources, unknown tree shapes, and dangling dataset bindings.

Instructions

List report-local data views: inputs, joins, filter IDs and exact references.

Includes single-query views, not only multi-source blends. Join type codes are returned without guessing enum meanings. Missing attached sources, unknown tree shapes and dangling dataset bindings are reported. No mutation, schema validity, runtime usage or deletion safety is inferred from this list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blends_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

readOnlyHint=true already covers the safety profile, yet the description adds genuine behavior: join type codes are returned raw without interpreting enum meanings, and the tool reports anomalies (missing attached sources, unknown tree shapes, dangling dataset bindings) rather than failing. It also explicitly disclaims inference of schema validity, runtime usage or deletion safety, which is exactly the kind of caveat an agent needs. Ordering and result-volume behavior are not described.

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?

The description is front-loaded with what is returned, then moves to caveats, in four dense sentences with no filler. The telegraphic, fragmentary style ('Join type codes are returned without guessing enum meanings') is efficient but occasionally terse enough to slow parsing.

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, so return values need no explanation, and the safety/limitation caveats are well covered. The gaps are the unaddressed optional parameter semantics and the absence of routing guidance versus overlapping siblings. For a read-only list tool this is adequate but not complete.

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% and the single parameter report_id is not mentioned at all in the description. It never says what happens when report_id is omitted, even though the schema makes it nullable with a null default, leaving a real ambiguity about whether the call spans all reports. The phrase 'report-local' only weakly implies the scoping role of 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?

The first sentence gives a specific verb and resource (list report-local data views) plus the concrete payload: inputs, joins, filter IDs and references. The second sentence usefully widens scope by noting single-query views are included, which prevents a common misreading. It stops short of distinguishing itself from siblings like blend_get or blends_joins, which return overlapping slices of the same data.

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 by the scoping language ('report-local', 'includes single-query views'), which tells the agent this is the broad enumeration call rather than a single-object fetch. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for narrower needs such as join details or a single blend.

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