Skip to main content
Glama

Datasource Sharing Get

datasource_sharing_get
Read-only

Retrieve a reusable datasource's access roles, sharing permission, and fingerprint so you can verify who can open or edit it before updating sharing settings.

Instructions

Who can open or edit a reusable datasource: members with owner/editor/viewer role, whether this account may share it, and the fingerprint for datasource_sharing_set.

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_sharing_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

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added value is the payload shape: permissions by role, a share-capability flag, and a fingerprint token. It says nothing about permission gating (e.g. what is returned when the caller is only a viewer) or why a fingerprint is needed, so behavioral disclosure beyond annotations is modest.

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 dense sentence with no filler, and the resource is front-loaded before the details of what is returned. It could have been broken up or led with an explicit verb, but nothing is wasted.

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?

For a two-parameter read tool with annotations and an output schema, the return values need not be restated, so the main remaining burden is the unexplained report_id parameter and any access prerequisites. Those gaps keep it at adequate rather than 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% for two parameters, so the description must carry the load and it does not mention either one. The nullable, default-null report_id is entirely unexplained, leaving the agent with no basis for deciding when to supply it versus passing null. Only the datasource_id concept is indirectly implied by the subject of the description.

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?

Names the resource (a reusable datasource) and what is returned: role-based access (owner/editor/viewer), whether this account may share it, and the sharing fingerprint. It also implicitly distinguishes itself from the sibling datasource_sharing_set by tying its fingerprint output to that tool. The verb is only implied by 'Get' in the name rather than stated in the description, so it falls just short of 5.

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?

The reference to 'the fingerprint for datasource_sharing_set' implies this tool is the read step preceding a sharing update, which is useful implied guidance. However, there is no explicit statement of when to use this versus datasource_get or datasource_settings_set, and no mention of prerequisites such as needing owner rights to see sharing state.

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