Skip to main content
Glama

Connect Integration

connect_integration

Starts a provider OAuth connection for a TestDino project and first checks status, returning already_connected when the integration is active.

Instructions

Start the provider OAuth/connect flow for a TestDino project. The tool first checks current status and returns already_connected instead of starting OAuth when the provider is connected.

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": {
      "projectId": "<projectId>",
      "provider": "<provider>"
    },
    "name": "connect_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoTestDino organization ID. Usually inferred from the PAT scope; pass explicitly if the token spans multiple orgs.
providerYesIntegration provider connected to this TestDino project.
projectIdYesTestDino project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID. Optional — derived from your PAT scopes when omitted; pass it explicitly if your PAT spans multiple organizations."New value: +"TestDino organization ID. Usually inferred from the PAT scope; pass explicitly if the token spans multiple orgs."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"TestDino project ID"
    • changedInput schema / properties / provider / description
      Previous value: -"Integration provider to connect (Required)."New value: +"Integration provider connected to this TestDino project."
  2. Addedv2.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-destructive but externally-facing action. The description adds genuinely new behavior beyond that: a pre-check of status and an idempotent short-circuit returning already_connected instead of starting OAuth. It does not disclose what the flow returns on the success path (e.g. an auth URL) or any user-interaction requirement.

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?

Two short sentences, zero filler, with the primary action front-loaded and the short-circuit condition second. Every sentence carries information the agent needs.

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 3-parameter flow-initiation tool with no output schema, the definition covers purpose and the key conditional return path, which is most of what an agent needs. It stops short of describing the success-path result (auth URL or redirect) that an agent would have to surface to a user.

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%, so projectId, orgId and the provider enum are fully documented in the schema. The description adds no parameter-level meaning (e.g. which providers support OAuth vs token auth, or when orgId matters), so the baseline 3 applies.

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: "Start the provider OAuth/connect flow for a TestDino project." Scope is clear (per-project, per-provider), but it does not explicitly name or contrast with the obvious sibling get_integration_status, leaving the distinction to inference.

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 by the verb – call this to initiate a connection. The description also notes the tool self-checks status, which reduces the need to call get_integration_status first, but it never says when not to call this, nor does it name the status sibling as an alternative or prerequisite.

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