Skip to main content
Glama

Open a Matchaa guest space

create_guest_context

Use this only when another Matchaa tool needs a guestToken and none exists yet in this conversation; create_tailored_resume opens a guest space itself, so do not call this before it. Opens a private guest space, without an account. Reuse the returned guestToken for every later Matchaa call in the conversation, including edits, and keep it private. A limited number of complete adaptations is free in a guest space; edits, previews and downloads do not use them. Do not open another guest space to get around that limit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
expiresAtYes
guestTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-ish but non-destructive, closed-world profile is covered. The description adds real substance beyond that: no account required, the returned token must be reused and kept private, and a limited number of complete adaptations are free. A 3 is appropriate because the description adds some useful context, such as the guest-space nature and privacy handling, but not rich behavioral depth like token expiry or response details.

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?

The exclusion and the precondition are front-loaded in the first clause, and no sentence is filler. Some sentences are comma-spliced and pack several rules at once, which slightly hurts scanability for a zero-parameter tool.

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?

Return values need not be described because an output schema exists. Given the tool's simplicity, the definition covers everything an agent needs: when to call, when not to, token reuse across subsequent calls, privacy handling, and the free-adaptation quota.

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 the schema has nothing to explain and the baseline of 4 applies. The description still usefully explains the output handle (guestToken) that every later call depends on.

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 states a specific verb and resource: it "opens a private guest space, without an account." It also distinguishes itself from create_tailored_resume, which "opens a guest space itself," so an agent can tell the two apart without inspecting either 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?

Explicit preconditions are given: use only when another tool needs a guestToken and none exists yet, and do not call before create_tailored_resume. It also tells the agent not to open a second guest space to circumvent the free-adaptation limit, which rules out the most likely misuse.

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