Skip to main content
Glama

close_test_session

Destructive

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Delete only this session's disposable test accounts and test game. Saved submission reports remain. Does not touch production accounts, builds or games.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "close_test_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes further by enumerating exactly what is destroyed (disposable test accounts and test game) versus preserved (saved submission reports) versus untouched (production accounts, builds, games). It also discloses the auth requirement (OAuth connection or Authorization: Bearer API key), which is behavioral context the annotations cannot convey.

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?

Three tight sentences with no filler, but the auth prerequisite is front-loaded ahead of the actual purpose, which delays the most important information. The destructive scope and preservation clauses are efficiently packed into a single sentence.

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 one-parameter destructive tool with no output schema, the description covers auth, destruction scope, and exclusions well. It is missing only the outcome signal an agent would want after a destructive call — whether the deletion is irreversible and what confirmation is returned.

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?

There is a single required parameter at 0% schema description coverage, so the schema does not explain sessionId at all. The phrase 'this session's' implies sessionId identifies the session to tear down, but the description never states format, whether it must be an active session, or what happens on an unknown ID.

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 verb (delete) and a tightly scoped resource (this session's disposable test accounts and test game), then bounds it further by noting that saved submission reports remain. That scoping lets an agent distinguish it from close_test_build and close_branch without consulting their schemas.

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 establishes the usage context implicitly (tear down at the end of a test session) and explicitly excludes production accounts, builds, and games, which routes the agent toward close_test_build for build cleanup. It stops short of naming an alternative tool outright or stating prerequisites such as whether the session must still be open.

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