Skip to main content
Glama

Get quiz authoring capabilities

get_authoring_context
Read-onlyIdempotent

Use first when making a quiz or game. Get supported formats, defaults, account hosting limits and access, and what people do only in Playloop. create_quiz creates a lobby; promise invitation links only when the result contains them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, closed-world, and non-destructive behavior. Beyond that, the description adds a useful output-dependent warning: invitation links should only be promised when the result contains them, which is behavioral context the annotations do not cover.

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 definition is compact and front-loads the key sequencing instruction. The final clause mixes sibling behavior with an output caution, which is slightly dense, but every sentence carries useful guidance.

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 zero-parameter, read-only context tool with an output schema, the description covers when to call it, what categories of information it provides, and a critical constraint about invitation links. The output schema can handle detailed return structure, so no further description is needed.

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 parameter semantics are not applicable and the baseline is 4. There are no inputs to explain or compensate for.

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 retrieval verb and names the exact resource: supported formats, defaults, account hosting limits and access, plus Playloop-only behaviors. It also distinguishes this preparatory tool from create_quiz, which is named explicitly as the tool that creates a lobby.

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 gives clear sequencing guidance with 'Use first when making a quiz or game' and names create_quiz as the downstream action. It does not state when not to use the tool or mention other authoring-related siblings, but the primary usage context is unambiguous.

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