Skip to main content
Glama

Open subscription connection settings

connect_subscription
Read-onlyIdempotent

Return the Account page URL to connect a subscription in your browser. Does not start authorization or accept authorization codes, tokens, cookies or secrets. Never ask the user to paste authorization secrets through MCP.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "connect_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description adds useful details beyond that, namely that it returns a URL without starting authorization and that secrets must never be pasted through MCP. It does not say what the URL contains, whether it expires, or how the provider choice affects the returned page.

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?

Three short sentences with the main action and the returned value front-loaded, followed by the safety constraints. No wasted wording, though the return-value sentence could be tighter.

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?

As a read-only tool with no output schema, the description adequately explains the return value (a URL) and the safety boundaries (no secrets). It is incomplete on the provider parameter and on what happens if no provider is supplied, which matters for correct invocation.

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 50%: workspace_id is documented ('from whoami'), but provider is an undescribed 4-value enum. The description says nothing about what provider selects, whether it is required, or what the default is, so it does not compensate for the gap even though the baseline for partial coverage is low.

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: it returns the Account page URL used to connect a subscription. It also draws a clear boundary against what siblings like remove_subscription or list_subscriptions do, though it names no alternative tool explicitly.

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?

The opening sentence establishes the use case: open the returned URL in a browser to connect a subscription. The following sentences set out exclusions: it does not start authorization or accept codes, tokens, cookies or secrets. There is clear context but no explicit 'use X instead' routing.

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