CueFrame

Search Fonts

search_fonts

Read-only

Search web font families by name/style — returns family names to use in composition/component params. Pass query (+ optional perPage ≤50). Read-only + free; surfaces the Google Fonts catalog (family + category + variants + css2 stylesheet URL). IMPORTANT: this searches the GOOGLE catalog, not what the render can actually draw. Only the faces vendored into the render page are guaranteed to rasterize; naming any other family gets you the generic fallback (Liberation Sans) with no error. Call list_render_fonts for the set you may actually choose from, WITH the admitted weights per family — treat that, not this catalog, as the list. An empty result set here means no match, or the upstream catalog was unavailable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "search_fonts"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	POST /fonts/search body.

Output Schema

Name	Required	Description	Default
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "__schema1": {
+    "exclusiveMinimum": 0,
+    "maximum": 50,
+    "type": "integer"
+  }
+}
```
- addedInput schema / properties / body / properties / perPage / $ref
```
Added value: +"#/$defs/__schema1"
```
- removedInput schema / properties / body / properties / perPage / exclusiveMinimum
```
Removed value: -0
```
- removedInput schema / properties / body / properties / perPage / maximum
```
Removed value: -50
```
- removedInput schema / properties / body / properties / perPage / type
```
Removed value: -"integer"
```
- addedInput schema / properties / body / properties / query / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / body / properties / query / maxLength
```
Removed value: -200
```
- removedInput schema / properties / body / properties / query / minLength
```
Removed value: -1
```
- removedInput schema / properties / body / properties / query / type
```
Removed value: -"string"
```
First observedOct 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/destructive=false) by disclosing a silent failure mode: unnamed or unvendored families fall back to Liberation Sans with no error. It also notes the tool is free, that it reads an upstream catalog, that results include category/variants/css2 URL, and that an empty set can mean upstream unavailability rather than no match.

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?

Front-loaded with purpose and return value, then the critical warning. A few clauses are mildly redundant ('treat that, not this catalog, as the list' restates the vendored-faces point), but the repetition is purposeful for a high-cost failure mode.

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

Completeness5/5

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

Even though an output schema exists, the description covers the one thing the schema cannot: that catalog membership does not imply renderability. Nested body structure and limits are handled by the schema; nothing needed to invoke or interpret this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics: query matches name/style (not just any string) and perPage is bounded at 50, framing how the parameters behave rather than merely restating them.

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?

States a specific verb and resource ('search web font families by name/style') and immediately says what it returns ('family names to use in composition/component params'). It explicitly distinguishes itself from the sibling list_render_fonts and from the render's actual font inventory, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for catalog lookup, but call list_render_fonts for the set you may actually choose from, 'treat that, not this catalog, as the list.' It also explains the empty-result condition, covering the when-not case.

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

All CueFrame tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.