Skip to main content
Glama
Sign In

upAPI

by io.github.DevinoSolutions
OverviewDiscussionsAdmin

Disconnect a platform account

disconnect_platform_account

Deletes a stored platform login (cookies), not an AI app connection. Needs a confirmToken. Refused for API keys.

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": {
      "id": "<id>"
    },
    "name": "disconnect_platform_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFrom list_platform_accounts
confirmTokenNoFrom the CONFIRMATION_REQUIRED reply.
organizationIdNoApproved workspace id only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a confirmToken from a CONFIRMATION_REQUIRED reply is mandatory, API-key targets are rejected, and the object actually removed is stored cookies rather than an app connection. One tension remains — the description says 'Deletes' while destructiveHint is false; that is defensible only if the action is treated as recoverable via reconnect, which the description never states.

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 terse clauses with zero filler, and the core disambiguation ('not an AI app connection') is front-loaded before the prerequisite and refusal rules.

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 small, non-idempotent removal tool with no output schema, the description covers what is removed, the confirmation gate, and a rejection case. It omits what an agent should do after removal (e.g., reconnect via connect_platform) and whether repeated calls behave differently, which is relevant given idempotentHint=false.

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 100% and every parameter already documents its source ('From list_platform_accounts', 'From the CONFIRMATION_REQUIRED reply', 'Approved workspace id only'). The description's mention of confirmToken merely restates the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Deletes a stored platform login (cookies)') and immediately excludes a confusable concept ('not an AI app connection'), which lets an agent separate this from the sibling 'disconnect' and the connection-listing tools without opening the schema.

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?

Provides clear when-not conditions: this is for stored platform logins, not AI app connections, and it is refused for API keys (pointing implicitly at revoke_api_key). It stops short of naming the alternative tools or stating the user-facing scenario that should select this one, so it falls short of a full 5.

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

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