Skip to main content
Glama

Datasource Parameters List

datasource_parameters_list
Read-only

Lists lossless parameter definitions and the source fingerprint for a Google Data Studio datasource, enabling agents to inspect schema and detect changes before editing.

Instructions

List lossless datasource parameter definitions and their source fingerprint.

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": {
      "datasource_id": "<datasource_id>"
    },
    "name": "datasource_parameters_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo
datasource_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description carries a reduced burden. It adds one genuine piece of behavioral information beyond the annotations: results include a source fingerprint, hinting at version/provenance data. It does not say what "lossless" means in practice or how the fingerprint should be interpreted.

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?

A single front-loaded sentence with no boilerplate or repetition. Nothing could be trimmed, but the terseness comes at the cost of the missing usage and parameter detail rather than through efficient density of information.

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?

The tool is simple, an output schema exists so return values need no explanation, and annotations cover safety. However, with 0% schema coverage on two parameters and no usage guidance, the definition leaves an agent unable to confidently decide how report_id changes the result or when this list is the right call.

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, so the description is the only place semantics could be supplied and it supplies none. Neither datasource_id (required) nor report_id (optional, nullable, defaulting to null) is mentioned, leaving the agent to guess what report_id scopes and why it is optional. This is a real gap for a call that requires a specific datasource identifier.

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 description names a specific verb ("List") and a specific resource ("datasource parameter definitions"), and adds that each entry carries a source fingerprint. This distinguishes it plainly from the mutation siblings datasource_parameters_upsert and datasource_parameters_delete. It loses a point because "lossless" is unexplained jargon that does not help an agent decide what it will get back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no routing to an alternative. The only implicit signal is the plural verb "List" versus the upsert/delete siblings. An agent gets no help deciding between this and, for example, datasource_get or datasource_dependencies when it needs parameter information.

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