Skip to main content
Glama

list_playbooks

Read-only

Lists stored NowAIKit playbook definitions from ServiceNow system properties, letting you set a limit for returned records.

Instructions

List stored NowAIKit playbook definitions (system properties nowaikit.playbook.*)

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_playbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.9.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context by disclosing that records come from system properties under the nowaikit.playbook.* prefix. It does not mention ordering, pagination, or what a returned entry looks like.

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?

A single compact sentence with the resource and source front-loaded; nothing is wasted. It is perhaps slightly too terse given the absence of return or pagination context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-optional-param read tool with annotations covering safety, the description is adequate: it names the resource and its backing store. It omits return shape and pagination behavior, which is acceptable since no output schema exists but leaves a small gap.

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%, so the limit parameter and its default of 25 are already fully documented in the schema. The description adds no additional semantics about the parameter, so the baseline 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 stored NowAIKit playbook definitions') and scopes the source ('system properties nowaikit.playbook.*'), which meaningfully separates it from a sibling like list_security_playbooks. It stops short of explicitly naming a sibling it is not, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no statement of when another listing tool would be preferable. The only implicit signal is the 'NowAIKit playbook' scope, leaving the agent to infer selection criteria.

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