Skip to main content
Glama

Get a link to connect an app

connect_app

A link the person opens to connect an app account to Fetch Hive (they sign in to the app there). You never see or handle their credentials. After they say it is done, check with list_connections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "connect_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe app id from list_connections, e.g. "slack" or "gmail".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the link is opened by the person, they sign in directly with the app, and the agent never sees credentials. It also names the follow-up verification step with list_connections. It does not mention link expiry or single-use constraints, but the added context is substantial.

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?

Three short sentences with no wasted words. The core purpose is front-loaded, followed by the credential-safety note and the next-step instruction, in a logical order.

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?

For a single-parameter tool with no output schema, the description covers the essential purpose, human-in-the-loop security behavior, and the recommended follow-up. It could be slightly more complete by noting what the link returns or any expiry behavior, but it is adequately complete.

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 description coverage is 100%, and the schema already explains that the app parameter is the app id from list_connections, with examples. The description reinforces the source but adds no further parameter meaning beyond 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 clearly states that the tool provides a link for a person to connect an app account to Fetch Hive. It is specific about the resource and action, though it does not explicitly distinguish itself from other link-getting siblings like get_claim_link or get_upload_link.

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 implied: call this when someone needs to connect an app account. The description adds workflow guidance to check list_connections afterward, but it does not explicitly state when to use this versus alternatives or any prerequisites/exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources