Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_playbook_list

Filter and list browser automation playbooks by origin, feature, tag, or verification status. Returns metadata only; retrieve full playbook separately.

Instructions

List per-feature playbooks. Filter by origin, feature slug, tag, or verifiable. Returns compact metadata only — call browser_playbook_get for the full body.

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

Input Schema

NameRequiredDescriptionDefault
originNo
featureNo
tagNo
verifiableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description must disclose behavior. States it returns 'compact metadata only', implying read-only and limited data. Mentions filtering by multiple criteria. Lacks details on pagination or limits, but adequate for a list tool.

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 sentences, no unnecessary words. Action verb ('List') leads, followed by filter list and comparison with sibling. Efficiently structured.

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?

Explains output nature ('compact metadata') and link to detailed tool. Mentions all 4 parameters as filters. Lacks details on default behavior, sort order, or maximum results, but these are acceptable gaps for a simple list operation.

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?

Schema coverage is 0%, so description must add semantic meaning. Explicitly names each filter parameter (origin, feature slug, tag, verifiable) as filters. Does not specify formats or allowed values, but provides sufficient context for parameter roles.

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?

Description specifies verb 'List', resource 'per-feature playbooks', and distinguishes from sibling 'browser_playbook_get' by noting compact metadata vs full body.

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?

Explicitly directs to 'call browser_playbook_get for the full body', providing a clear alternative. Lists filter parameters, implying when to use filters, but does not explicitly state when not to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools