Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

connect

Read-only

Shows which of the user's Google Workspace, Atlassian and Notion accounts are connected, and gives a one-click link to connect each one that is not. Call it first when you do not know what is connected, and whenever a tool says a provider is not connected. Each provider's tools are only listed once it is connected. Pass service to get a link for that provider even when it is already connected, to add another account. The link is for the user to open in their browser: it works once and expires after ten minutes.

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

Input Schema

NameRequiredDescriptionDefault
serviceNoOne provider to report on, with a link even when it is already connected. Omit it to report on all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description adds real operational context beyond that: provider tools are not even listed until connected, the link is for the user's browser rather than the agent, it is single-use, and it expires in ten minutes. Those details materially change how an agent must hand off the result, and none of them are derivable from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: what it does, when to call it, and how the link/parameter behaves. The core capability is front-loaded and there is no filler or repetition.

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 single optional-enum read tool this covers purpose, triggers, link lifecycle, and the parameter's dual role, with no output schema needed since the return shape is described in prose. The unresolved overlap with list_connected_accounts is the one thing an agent could still get wrong.

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 coverage is 100% and the enum property already documents both modes (omit for all, specify for one with a link even when connected). The description's sentence about 'service' largely restates the schema. The 'to add another account' rationale is a small genuine addition but not enough to exceed the baseline.

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?

States a specific verb and resource: shows which Google Workspace, Atlassian and Notion accounts are connected, plus a connect link for each missing one. That is far more than a restatement of the name. It loses a point because the sibling tool 'list_connected_accounts' appears to cover adjacent ground and the description never distinguishes the two, leaving the agent to guess which to call.

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?

Gives two concrete call triggers: call it first when connectivity is unknown, and whenever another tool reports a provider not connected. It also explains the 'service' escape hatch for adding a second account. The only gap is that it offers no guidance versus the similarly named list_connected_accounts sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources