Skip to main content
Glama

environment_connect

Idempotent

Initiates Visual Studio's Connect to Dataverse sign-in, lets you interactively choose an environment and solution, then reports the connected environment details once sign-in completes.

Instructions

Start Visual Studio's own Connect to Dataverse command and wait for the user to complete the interactive sign-in and solution selection in Visual Studio, then describe the connected environment. The sign-in itself cannot be automated.

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo

Output Schema

NameRequiredDescriptionDefault
okYes
busyNo
errorNo
finOpsNo
reasonNo
tenantIdNo
connectedNo
dataverseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely new behavior: the call blocks and waits for a human, so it can hang for a long time, and it cannot complete without manual interaction. It does not disclose what happens on timeout or what state changes the connect command leaves behind.

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?

Two tight sentences, front-loaded with the action and followed by the blocking/automation constraint. No 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?

An output schema exists, so return values need not be explained, and the description covers the essential interaction model for a blocking, human-in-the-loop tool. The gaps are timeout behavior and what workspace/connection state the command persists, which matter for a non-readOnly tool.

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?

The single parameter timeoutMs has 0% schema description coverage and is never mentioned in the description. The phrase 'wait for the user to complete' implicitly explains why a timeout exists and that the wait may be long, but the parameter name, range and default are left entirely to the schema.

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 resource ('Start Visual Studio's own Connect to Dataverse command'), states the blocking/waiting behavior, and says it ends by describing the connected environment. It is distinguishable from a plain environment_info-style tool, though it never names the sibling that would give the same information after a connection already exists.

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 clearly establishes the context of use: an interactive, user-driven sign-in and solution selection that the agent cannot automate. It does not name an alternative for the already-connected case or state when not to use it, but the constraint 'the sign-in itself cannot be automated' is a strong practical guideline.

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