Skip to main content
Glama

List Examples

list_examples
Read-only

Discover the complete playable examples bundled with this release. Returns compact summaries and exact refs; does not load or play anything. Use schema_version: 1. Limit defaults to 20 (1–100); optional source/id filters and opaque cursor; kind, when supplied, must be invention. Copy a returned ref into describe_example.

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": {
      "schema_version": "<schema_version>"
    },
    "name": "list_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
kindNo
limitNo
cursorNo
sourceNo
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, but the description adds real behavioral detail: results are summaries plus refs rather than full payloads, nothing is loaded or played, the cursor is opaque, and the default/maximum page size. These are traits not derivable from the annotations or schema.

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?

It is dense and front-loaded, leading with what the tool does and the read-only boundary before the parameter notes. Some clauses are telegraphic ('kind, when supplied, must be invention'), but no sentence is filler.

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 read-only listing tool with no output schema, it covers scope, return shape (compact summaries plus exact refs), pagination, and the natural next call. Only the id parameter's meaning is left implicit, which is a modest gap for a 6-parameter tool.

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?

With 0% schema description coverage across 6 parameters, the description carries the full burden and largely does: it explains limit's default and bounds, that cursor is opaque, that kind must be 'invention' when supplied, and that source/id act as filters. Gaps remain — id's semantics and the meaning of the source values are unexplained, and the stated range 1–100 does not match the schema's minimum of 0.

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 concrete verb and resource ('Discover the complete playable examples bundled with this release') and immediately bounds the operation ('Returns compact summaries and exact refs; does not load or play anything'). That last clause cleanly separates it from siblings like play_preview and describe_example.

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 actionable usage context: 'Use schema_version: 1', 'Limit defaults to 20 (1–100)', and the handoff instruction 'Copy a returned ref into describe_example', which routes the agent to the correct follow-up tool. It does not state exclusions beyond the 'does not load or play anything' boundary, so it falls short of a full when/when-not matrix.

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