Skip to main content
Glama
Sign In
p21

p21

by mocchan0221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List fonts

p21_fonts
Read-only

Lists installed font families usable in the font field of text elements, with an optional case-insensitive query filter to find available fonts.

Instructions

List installed font families usable in the font field of text elements.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that results are installed font families and are valid inputs for the `font` field, but says nothing about return format, ordering, or what happens with zero matches.

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?

A single tight sentence that front-loads the action and immediately states the practical purpose. No filler or redundancy.

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 one-parameter, read-only listing tool with full schema coverage and annotations covering safety, the description supplies what's needed: what is listed and how the values are consumed. Only return-shape details are absent, which is minor given there is no output schema requirement.

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 coverage is 100% for the single optional `query` parameter, so the schema already explains the case-insensitive filter. The description doesn't mention the filter at all, so it adds nothing beyond the schema; 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?

The description uses a specific verb and resource ('List installed font families') and adds the practical scope that results are usable in the `font` field of text elements. It's clearly distinct from siblings like p21_render or p21_print, though it doesn't explicitly name any of them as alternatives.

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?

Usage is only implied through the phrase 'usable in the `font` field of text elements' — an agent can infer this is a lookup to call before setting a font. There is no explicit when-to-use, when-not-to-use, or reference to a sibling 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