Skip to main content
Glama

get_setup_guide

Read-onlyIdempotent

Retrieve detailed setup instructions for configuring email providers such as Microsoft OAuth2, Gmail, and Zoho.

Instructions

Get detailed setup instructions for email providers (Microsoft OAuth2, Gmail, Zoho, etc.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the content is 'detailed setup instructions' for multiple providers, but it does not say whether all providers' guides are returned at once or whether the response is static reference text — notable given the tool has zero parameters.

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?

A single well-formed sentence with the resource and the scope front-loaded and zero filler. Nothing could be removed without losing information.

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?

With no parameters, an existing output schema, and full annotation coverage, the description only needs to explain the intent — which it does. It stops short of clarifying that the guide is provider-agnostic reference material returned in full, leaving an agent unsure how to target a specific provider (e.g., Microsoft OAuth2 vs Zoho).

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?

There are no parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The one caveat is that enumerating provider names could momentarily suggest a provider argument exists, which the empty schema contradicts, but the description does not actively mislead.

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 ('Get detailed setup instructions') and scopes it to email providers, naming concrete examples (Microsoft OAuth2, Gmail, Zoho). It is clearly distinguishable from the sibling mail-operation tools, though it never explicitly says it is the documentation/onboarding counterpart to them.

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?

Usage is only implied: an agent should call this when it needs setup/config guidance for a provider. There is no explicit when-to-use trigger (e.g., 'call before imap_verify_account fails') and no statement about alternatives or exclusions.

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