Skip to main content
Glama

My connected AI apps and keys

portal_connections_list
Read-onlyIdempotent

The AI apps and personal API keys currently connected to your Barmaan account: app name, status, when it connected, when it was last used, and exactly what each one may do. Also returns what no connection can ever do and the official server URL. Disconnecting an app is only possible on the website (Portal, MCP connections).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "portal_connections_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real context: the output includes what no connection can ever do, the official server URL, and per-connection capability scope. It also discloses the important behavioral boundary that disconnection cannot happen through this tool, which is not covered by any annotation.

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?

Two sentences, front-loaded with the resource and its returned fields, followed by the capability/URL note and the disconnection caveat. Nothing is redundant, though the clause 'what no connection can ever do' is slightly abstract and could have been stated more concretely.

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?

With no output schema, the description carries the burden of explaining return content, and it does so by enumerating the per-connection fields plus the two extra payloads (prohibited capabilities and official server URL). Safety semantics are handled by annotations, and no parameters exist, so the remaining gap is only the lack of named field keys.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the documented baseline for a parameterless schema applies. The description correctly implies an unfiltered full listing rather than suggesting any input the agent might try to supply.

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 names a specific resource (AI apps and personal API keys currently connected to the Barmaan account) and enumerates the attributes returned: app name, status, connection time, last-used time, and granted capabilities. It does not differentiate itself from siblings such as my_apps_list or portal_mcp_permissions_get, so an agent must infer the boundary, but the core purpose is unambiguous.

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 clearly scopes out an action an agent might attempt: disconnecting is only possible on the website (Portal, MCP connections), which is a useful when-not statement with an alternative location. It does not explicitly say when to prefer this over sibling listing tools, but the read-only inventory framing implies the use case well.

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