Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Connected Sessions

alterlab_sessions
Destructive

List the site sessions the user has connected, with each one's health, domains and scopes, or revoke one so it can no longer be used. action=list (default) is read-only; action=revoke needs session_id and cannot be undone, so only revoke when the user asks. Cookie values are never returned. A handle from here goes into alterlab_task_start.

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": "alterlab_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNolist (default) or revoke
session_idNoSession handle to revoke. Revoke only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses that revocation is irreversible, that cookie values are never returned (an important data-privacy fact), and that returned handles feed alterlab_task_start. It does not describe pagination or how health is represented, but the added context is substantial given annotations already flag destructiveness.

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?

Four short clauses, front-loaded with what is listed and what is returned, followed by mode semantics and the safety constraint. No sentence is wasted and the riskiest fact (irreversibility) appears before any downstream pointer.

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 output schema, the description compensates by enumerating the returned fields (health, domains, scopes) and by noting that cookie values are excluded. For a two-parameter tool with a destructive branch, nothing an agent needs in order to call it safely is missing.

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 both parameters are already documented as 'list (default) or revoke' and 'Session handle to revoke. Revoke only'. The description restates the default and the revoke-only constraint rather than adding new syntax or format details, so the baseline of 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?

The description names a specific resource (site sessions the user has connected) and covers both operations: listing with health, domains and scopes, and revoking a single session. It also names the downstream sibling alterlab_task_start, so the agent can place this tool in a workflow without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that action=list is the default and read-only, that action=revoke requires session_id, and gives an explicit when-not condition: 'only revoke when the user asks'. That is the exact routing guidance an agent needs to choose between the two modes.

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

All mcp-server 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