Skip to main content
Glama
Sign In

upAPI

by io.github.DevinoSolutions
OverviewDiscussionsAdmin

Connect a platform

connect_platform

Connects a platform login (cookies), not an AI app connection. Returns a one-time link and steps for the user to log in and hand upAPI their session. Relay the steps; never ask for cookies in chat. 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": {
      "platform": "<platform>"
    },
    "name": "connect_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional account name
platformYesPlatform
organizationIdNoApproved workspace id only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the return shape (one-time link plus login steps), the user-mediated handoff of session cookies, the security instruction to relay steps and never ask for cookies in chat, and the API-key refusal behavior. These are exactly the operational and safety details an agent needs.

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?

The description is compact and front-loaded: it states the action, distinguishes it from alternatives, describes the return, gives the user handoff procedure, and notes refusal for API keys. Every sentence carries useful information.

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 multi-step authentication tool with no output schema, the description covers the important output and safety behavior well. Minor omissions, such as link expiration or how to verify the resulting account, are not fatal because the schema and sibling tools cover nearby operations.

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%, so the input schema already documents the platform enum, optional label, and organizationId. The description adds context about the platform login flow but does not add parameter-specific meaning beyond the schema.

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?

The description states a specific action and resource: connecting a platform login using cookies, and explicitly distinguishes it from an AI app connection. An agent can immediately understand what this tool does and what it does not do.

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?

It gives clear usage context and exclusions: use for platform logins rather than AI app connections, and it is refused for API keys. It does not name a specific sibling alternative, but the when-not guidance is explicit enough to route the agent correctly.

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