Skip to main content
Glama
rjenks
by rjenks

build_list_backgrounds

List Pathfinder 2e backgrounds from the official rules database for character creation, with optional name filtering and legacy content inclusion. Each entry displays trained skills and granted items.

Instructions

List backgrounds, optionally filtered by name substring.

`trained_skills` (`{"fixed": [skill slugs], "lore": [Lore skill names]}`)
and `granted_items` (`[{level, name, uuid}]`, `level` always null for a
background -- granted at character creation) come straight from the
background item's own structured `system.trainedSkills`/`system.items`
fields, the same mechanism `build_list_classes` already exposes for
classes -- e.g. Field Medic: trained_skills `{"fixed": ["medicine"],
"lore": ["Warfare Lore"]}`, granted_items `[{"name": "Battle
Medicine", ...}]`.

`include_legacy` (default False): excludes pre-Remaster/OGL-flagged
backgrounds unless set -- 54% of all backgrounds are legacy-flagged and
still fully playable, the single largest exclusion of any pack this
filter touches. See `_legacy_filter_sql`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo
include_legacyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses that trained_skills and granted_items come from specific system fields, that level is always null, and details the significant impact of include_legacy (54% legacy-flagged, still playable). This provides meaningful behavioral context beyond just 'list'.

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 description is moderately detailed but well-structured, with separate sections for output fields and include_legacy. The mention of `_legacy_filter_sql` is cryptic but not overly distracting, and each substantial part earns its place.

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?

Given the output schema exists, the description adds important context by explaining the nested structure of trained_skills and granted_items and the legacy filter's practical implications. It covers the key aspects needed for an AI agent to use the tool correctly, though it omits potential details like ordering or pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description thoroughly explains both parameters: filter as a name substring and include_legacy's default and meaning. It also gives concrete examples of output structures, adding context beyond the schema.

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 clearly states it 'List backgrounds' with an optional name substring filter. This specific verb+resource combination unambiguously distinguishes it from sibling tools like build_list_classes and build_list_ancestries.

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?

The description implies usage for retrieving background lists and references build_list_classes for comparison, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. It explains parameter behavior but not usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rjenks/pf2e-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server