Skip to main content
Glama

Acquire session

acquire_session
DestructiveIdempotent

Add a marketplace session you are entitled to (free, bought, or granted) to your private library. Never buys anything: for a paid listing it returns status=payment_required with the price and the listing URL.

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": {
      "id": "<id>"
    },
    "name": "acquire_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMarketplace listing id (from search_sessions).
tenantNoOwning workspace of a marketplace listing (from search results). Optional.
versionNolatest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that no charge occurs and describing a concrete failure/edge return (status=payment_required with price and listing URL). It leaves the destructiveHint=true unexplained, however, and 'Add ... to your private library' reads as purely additive, so an agent gets no warning about what could be overwritten.

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?

Two sentences, zero filler, with the core action front-loaded and the critical 'it never spends money' caveat immediately after. The exact return token status=payment_required is more useful than prose would be.

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 three-parameter tool with no output schema, it covers the gating condition and one important non-success return shape. The success response (what the library entry looks like, whether re-acquisition is a no-op given idempotentHint) is left implicit, which is the remaining gap.

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 67% and the schema already documents id, tenant, and version origins ('from search_sessions', 'owning workspace', 'from search results'). The description adds no per-parameter meaning such as how version interacts with entitlement or whether tenant is needed for ambiguous ids, so the baseline 3 applies.

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?

States a concrete verb and resource: 'Add a marketplace session ... to your private library,' with the entitlement precondition spelled out (free, bought, or granted). It implicitly separates itself from the purchase flow by declaring 'Never buys anything,' though it does not name the purchase sibling (request_purchase) directly.

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?

Gives a clear eligibility condition (you must be entitled to the listing) and signals the fallback path for paid listings, which steers an agent toward the purchase-request tooling instead. It stops short of naming that alternative or stating explicit exclusions, which is why it is not a 5.

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.