Skip to main content
Glama

list_private_scenarios

Read-onlyIdempotent

List your private interview scenarios (summaries, paginated). Requires private_scenarios:read.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page. Omit for the first page; nonpositive values normalize to 1. Continue pagination when total exceeds the returned items.
pageSizeNoItems per page, normally 1..50. Omit or use a nonpositive value for 20; larger values are capped at 50.

Output Schema

NameRequiredDescriptionDefault
pageYes
itemsYes
totalYes
pageSizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: an authorization scope requirement and the fact that results are paginated summaries rather than full records.

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 compact sentences, nothing wasted, with the resource and response shape front-loaded and the permission requirement trailing as a caveat.

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?

An output schema exists so return values need not be described, and both parameters are fully documented in the schema. Adding the required scope covers the main remaining gap for a simple read-only list tool.

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 description coverage is 100%, and the schema spells out page normalization, defaults of 20, and the 50 cap. The description only gestures at pagination ('paginated') without adding meaning beyond that, so the baseline of 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 specific verb and resource ('List your private interview scenarios') plus the shape of the response ('summaries, paginated'), which separates it from get_private_scenario and list_interviews. It does not explicitly name a sibling it is not, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'your private ... scenarios', and the required scope 'private_scenarios:read' is a useful precondition. There is no explicit when-to-use/when-not guidance or pointer to an alternative for fetching a single full scenario.

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