Skip to main content
Glama

Datasource Get

datasource_get
Read-only

Read a datasource's draft and published definitions, including fields, formulas, types, and credentials. Retrieve the full configuration needed to audit or edit a datasource by UUID or URL.

Instructions

Read a source's draft and published definitions, fields, formulas, types, credentials.

datasource_id is a UUID or a datasource URL. No report is needed; see the datasource-scope rule in the server instructions.

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_get"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing that BOTH draft and published definitions are returned and that credentials are included in the payload — a meaningful sensitivity note an agent would not otherwise know.

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?

Three short sentences, front-loaded with the resource list and followed by parameter format and scoping notes. No filler, though the dangling pointer to server instructions slightly weakens self-containment.

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?

An output schema exists, so return values need not be spelled out, and readOnlyHint covers safety; the description covers format of the key identifier and the draft/published scope. The unexplained optional report_id and reliance on an external rule are the remaining gaps.

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

Parameters3/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 burden. It does add meaning for datasource_id (UUID or datasource URL), which the bare 'string' schema does not, but the optional report_id parameter is never mentioned and sits awkwardly against the line 'No report is needed.'

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 uses a specific verb and enumerates the resources returned: 'Read a source's draft and published definitions, fields, formulas, types, credentials.' The clause 'No report is needed' implicitly separates it from report-scoped siblings, but no alternative tool is named explicitly.

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?

It gives one useful scoping cue ('No report is needed') and defers to a 'datasource-scope rule in the server instructions' for the rest. There is no explicit when-not guidance or comparison against sibling reads such as datasource_sharing_get or datasource_parameters_list, so usage is only implied.

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