Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

Confirm the connection

confirm_connection
Idempotent

Confirms the API key works and tells Emailchaser which AI assistant connected. Use it when the user connects Emailchaser or asks to confirm or check the Emailchaser connection: it records the assistant and time on the key, which the app's API & MCP page watches to show the user you are in, and completes the 'Connect your AI' onboarding step. Idempotent: repeat calls simply refresh the record. Works with read-only keys as well as read & write keys.

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

Input Schema

NameRequiredDescriptionDefault
agentNoYour name in any form, e.g. claude, chatgpt, cursor, gemini. Normalized to a short lowercase identifier and echoed back

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing what the write actually does: records the assistant and timestamp on the key, surfaces that record on the app's API & MCP page, and completes the 'Connect your AI' onboarding step. It also explains why idempotency holds ('repeat calls simply refresh the record') and states an auth boundary the annotations cannot express: read-only keys are accepted.

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?

Core purpose is front-loaded and every clause carries information, but the single long colon-and-comma sentence bundles trigger, side effect, onboarding, idempotency, and auth scope together. Splitting these would improve scanability without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, no output schema, and annotations covering safety and idempotency, the remaining burdens are trigger conditions, side effects, and auth scope — all addressed. Nothing an agent needs to invoke this correctly is missing.

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 'agent' parameter is already fully documented in the schema, including normalization and echo-back, so schema coverage is 100%. The description's 'records the assistant and time on the key' loosely maps to it but adds no format or constraint detail beyond the schema, leaving this at 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 ('Confirms the API key works') plus the registration side effect ('tells Emailchaser which AI assistant connected'). An agent can tell this apart from data-mutation siblings, though it never names a nearby tool such as connect_sender_email to rule out confusion.

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 an explicit trigger: 'Use it when the user connects Emailchaser or asks to confirm or check the Emailchaser connection.' No when-not-to-use clause or named alternative, but the trigger is concrete enough to act on.

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

All Emailchaser 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