Skip to main content
Glama
the-real-talk

the-real-talk

list_available_fonts

Lists installed font families and styles, optionally filtered by name substring, so you can find available fonts for Figma design work.

Instructions

List installed font families and styles, optionally filtered by a name substring.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'List installed' weakly implies a read-only enumeration, but nothing is said about ordering, default result size, case sensitivity of the substring match, or whether families and styles come back grouped or flat.

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, front-loaded with the action and resource, followed by the one qualifier that matters. 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 two-optional-parameter read-only listing tool with no output schema, this covers the essentials an agent needs to make the call. The unexplained limit semantics and the unstated shape of results (flat vs. grouped family/style) are the only meaningful gaps.

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 0%, so the description must compensate. It clarifies that filtering is a substring match against a name, which goes beyond the bare 'query: string' schema, but the 'limit' parameter (1-200) is never mentioned or explained in the description or schema.

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 installed font families and styles', with the optional substring filter noted. The resource (fonts) is clearly distinct from the sibling list tools (list_channels, list_pages), though the description never explicitly contrasts itself with them.

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 phrase 'optionally filtered by a name substring' implies when to pass a filter, but there is no explicit when-to-use or when-not guidance, no prerequisites, and no named alternative for related font or style queries.

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