Skip to main content
Glama

What my connections may do

portal_mcp_permissions_get
Read-onlyIdempotent

For each AI app and personal key connected to your Barmaan account: its access level, which capabilities it was granted, calls in the last 24 hours and when it last ran. Also returns the capability library and what no connection can ever do. Removing a connection's edit access is only possible on the website (Portal, MCP permissions); this tool is read-only.

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_mcp_permissions_get"
  }
}

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, non-destructive, and closed-world behavior. The description adds useful behavioral context: it returns per-connection access, capabilities, 24-hour call counts, last-run time, the capability library, and universal prohibitions, and it clarifies that edit-access removal is website-only. It does not cover auth or rate limits, but those are less critical here.

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-loads the returned information before adding the capability library and the website-only removal caveat. Every sentence contributes to understanding the tool's output or limits.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters, no output schema, and rich annotations, the description supplies enough detail about what is returned and what the tool cannot do. An agent can decide to call it and interpret the result without needing more structured output documentation.

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?

There are zero input parameters, so the schema imposes no semantic burden. The description does not need to explain parameters, and the baseline for a no-parameter tool is 4.

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 states a specific read operation over AI apps and personal keys, listing access level, granted capabilities, recent calls, and last run. It is clear what the tool returns, but it does not explicitly name sibling tools such as portal_connections_list or portal_mcp_activity_list to differentiate scope.

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?

It gives a clear when-not: removing edit access must be done on the website, and the tool is read-only. However, it does not state when to choose this overview versus portal_connections_list or portal_mcp_activity_list, so alternative selection is left implicit.

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