Skip to main content
Glama

get_private_scenario_practice_link

Read-onlyIdempotent

Get a ready scenario's stable website practice link without reading its content. Requires private_scenarios:practice. Opening the link does not start an interview or spend credits; the website asks the owner to choose funding.

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": {
      "scenarioId": "<scenarioId>"
    },
    "name": "get_private_scenario_practice_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioIdYesCanonical UUID of your owned scenario, returned by create_private_scenario or list_private_scenarios. Do not invent an ID or substitute a practice-reference ID. Ownership comes from the token, not a userId argument.

Output Schema

NameRequiredDescriptionDefault
urlYes
questionRefYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the required scope and, critically, that opening the link does not start an interview or spend credits and that funding is chosen by the owner on the website. That is exactly the side-effect information an agent needs before handing a link to a user.

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?

Three short sentences, front-loaded with what the tool returns, then the permission gate, then the side-effect clarification. No filler and no repetition of schema or annotation data.

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?

For a single-parameter read tool with a full output schema and rich annotations, the description covers the remaining unknowns: permissions, link stability, and the consequence of opening it. Nothing an agent needs in order to call it or explain the result 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% and the scenarioId property description is unusually rich (UUID source, ownership from token, no practice-reference IDs), so the schema does most of the work. The description only adds the qualifier 'ready scenario's', which implies the ID must reference a validated scenario without spelling out error behavior.

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 ('Get a ... stable website practice link') and scopes it against the sibling read operation with 'without reading its content', so an agent can tell why it would pick this over get_private_scenario. 'Stable' and 'ready' also signal the nature of the return value.

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 names the prerequisite ('Requires private_scenarios:practice') and gates usage on the scenario being 'ready', which is actionable when-to-use context. It stops short of explicitly naming an alternative tool or stating when not to use it, so a 4 rather than 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.

Resources