Skip to main content
Glama

environment_info

Read-only

Describe the Dataverse or Finance and Operations environment Visual Studio is connected to, including URLs, type, versions, tenant, and busy status; it prompts to connect if disconnected and allowed.

Instructions

Describe the Dataverse / online Finance and Operations environment Visual Studio is connected to (URLs, type, versions, tenant, busy flag). If Visual Studio is not connected it opens its connection wizard, so this refuses unless allowPrompt is true or a connected environment was already seen in this session. No access token is ever returned.

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

Input Schema

NameRequiredDescriptionDefault
allowPromptNo

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

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the non-obvious side effect that the tool can open Visual Studio's connection wizard, the guard that prevents that (allowPrompt), and a security-relevant guarantee that no access token is ever returned. The wizard-opening behavior is exactly the kind of thing annotations alone would hide behind a readOnlyHint.

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 tight sentences, front-loaded with what is returned, then the gating condition, then the security note. The parenthetical field list is dense but earns its place; 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 needn't be detailed, and the session/permission caveat plus the no-token promise cover the risky parts of a read-and-probe tool. A single pointer to environment_connect for the not-connected case is the only missing piece.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single param has only a type and default, so the description carries the load — and it does explain that allowPrompt governs whether the connection wizard may be launched and that the default posture is to refuse. That is the meaningful semantic for the parameter; only the exact default value is left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Describe the Dataverse / online Finance and Operations environment Visual Studio is connected to' — and enumerates what is reported (URLs, type, versions, tenant, busy flag). It also distinguishes itself from a connecting tool by noting it refuses rather than establishing a connection, so an agent can separate it from environment_connect without opening the schema.

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 gives a clear precondition — a connected environment seen in this session, or allowPrompt=true — and states that failing that, the tool refuses. What it does not do is point the agent at environment_connect as the way to establish a connection, so the recovery path is left implicit.

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