Skip to main content
Glama

Datasources List

datasources_list
Read-only

List datasources attached to a Data Studio report, or retrieve all reusable account datasources when no report is open or all_accessible is true.

Instructions

List the sources attached to a report, or every datasource the account can open.

With all_accessible=true, or with no report open, lists the account's reusable datasources (id, name, owner, modified) without any report. Otherwise lists the sources attached to the report; isEmbedded distinguishes shared sources.

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": "datasources_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo
all_accessibleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety, and the description adds meaningful behavior beyond it: all_accessible or an absent report switches scope to reusable account datasources, and isEmbedded identifies shared sources. It still does not discuss permissions, pagination, or rate limits.

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 the main list behavior and then explains the mode nuance in a compact second paragraph. There is minor repetition between the opening sentence and the elaboration, but no wasted filler.

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 two-parameter read-only list tool with an output schema, the description covers the important scope decision and identifies a distinguishing return field. It is nearly complete, with only minor operational details such as permissions left unstated.

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?

With 0% schema description coverage, the description carries the burden and explains the key effect of all_accessible=true and the report-attached fallback behavior that corresponds to report_id. It does not spell out the parameter names or null/default semantics explicitly, but the operational meaning is clear.

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?

The description states a specific verb and resource (list datasources) and explicitly distinguishes two scopes: sources attached to a report versus all reusable account datasources. This scope language is enough to separate it from a sibling such as datasources_remove_from_report without needing the sibling named.

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?

It gives clear mode-selection guidance: use account-level listing when all_accessible=true or no report is open, otherwise list report-attached sources. The conditions are explicit, though it does not name alternative tools or additional exclusions.

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