Skip to main content
Glama

List fonts

list_fonts
Read-only

Lists available font families for text: fonts installed on this computer plus, when you pass a presentation path, the font files added to that project. Filter by name.

Instructions

Lists the font families available for text: the fonts installed on this computer plus, when path is given, the font files added to that presentation.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional project, to include its added fonts.
limitNo
queryNoOnly families whose name contains this (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by clarifying that results are a union of local system fonts and presentation-scoped fonts, which is not derivable from annotations or schema. It stops short of describing ordering or the effect of the undocumented 200-item cap.

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 sentence with zero filler, front-loading the verb and resource before the conditional path behavior. Every clause earns its place and nothing is repeated from the annotations or schema.

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 read-only list tool the description covers purpose and the one behavioral conditional, but it leaves the default limit of 200 undocumented anywhere, meaning an agent cannot tell whether results may be silently truncated. With no output schema, a brief note on what a family entry looks like or on result ordering would have closed the remaining 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 coverage is 67%, with `path` and `query` documented inline; the description reinforces `path` by clarifying it means a presentation whose added fonts get included. The `limit` parameter has no description in either the schema or the description, so truncation behavior remains unexplained. Marginal added meaning over the schema, consistent with a baseline 3.

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 gives a specific verb and resource ('Lists the font families available for text') and immediately defines the scope: system-installed fonts plus fonts attached to a given presentation. That scope statement distinguishes it from mutation siblings like add_font, which add rather than enumerate. An agent knows exactly what this returns without opening the schema.

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?

The description explicitly tells the agent when the `path` argument changes behavior ('when `path` is given, the font files added to that presentation'), which is the main usage decision for this tool. It does not name any alternative tool or state when not to call it, but no obvious competing list tool exists among the siblings, so the gap is minor.

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