Skip to main content
Glama
flin-microsoft-ads-mcp

flin-microsoft-ads-mcp

by flin-agency

connection_status

Read-only

Inspect Microsoft Ads connection setup without exposing secrets, and optionally test live account discovery to confirm credentials work.

Instructions

Inspect setup without exposing secrets; optionally test live account discovery.

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

Input Schema

NameRequiredDescriptionDefault
check_liveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true. The description adds genuinely useful context beyond them: the response is sanitized ('without exposing secrets') and the live test performs real account discovery. It stops short of describing what is actually returned or the cost/side effects of a live probe.

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?

One compact sentence with the safety assurance front-loaded ahead of the optional behavior. Nothing is wasted, though the terseness comes at the cost of naming the actual system being inspected.

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?

The tool is simple (one optional boolean, no output schema), so little explanation is required, and the secret-redaction note covers the main behavioral risk. However, 'setup' is never concretized and the return value is left undefined, which matters because there is no output schema to fall back on.

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 0% and the single parameter 'check_live' is undocumented in the schema. The phrase 'optionally test live account discovery' gives the agent the meaning of that flag, but not its cost, failure modes, or default behavior beyond the schema's default=false.

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

Purpose3/5

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

The description gives a verb ('Inspect') and a vague resource ('setup'), plus an optional live check. It never states what connection is being inspected (ad account, API credentials, workspace), so an agent must infer that from the name alone. It does not distinguish itself from the sibling auth_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no exclusions: nothing says to prefer this over auth_status or list_accounts, nor when a live check is warranted versus a cheap static inspection. 'Optionally test live account discovery' is the only hint about choosing the check_live path.

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