Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

search_fonts

Read-onlyIdempotent

Search the font catalog that the cloud video renderer can load (Google Fonts library + project-bundled custom fonts). Use this when an export reports unsupported fonts or when picking fonts for motion-graphic items. Returns the canonical family name you use verbatim as fontFamily in motion-graphic code or properties. Substring-matches on the family name AND on native-name aliases (case- and punctuation-insensitive), so you can look up bundled Chinese fonts by their Chinese name — pass a fragment such as "inter", "playfair", "noto sc", "新青年", or "得意黑".

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": {
      "query": "<query>"
    },
    "name": "search_fonts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSubstring to match against font family names or their native-name aliases (e.g. a Chinese font name). Case- and punctuation-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description is not carrying the safety burden. It still adds real value: matching is substring-based across family names AND native-name aliases, case- and punctuation-insensitive, and the result is the canonical family name to be used verbatim as `fontFamily`. It omits behaviors like empty-result handling or result caps.

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-loads the resource and scope, then usage triggers, then return-value contract, then matching semantics — a logical order with no filler. The parenthetical asides make one sentence dense, so it is not maximally tight, but every sentence 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?

For a one-parameter read tool with full annotations and no output schema, the description covers what an agent needs: when to call it, what matching means, and that the returned family name is used verbatim as `fontFamily`. Only absent detail is what an empty result looks like, which is a minor gap.

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?

With 100% schema coverage the baseline is 3, and the description earns a bump by showing concrete fragment forms ("inter", "playfair", "noto sc", "新青年", "得意黑") that demonstrate how to exploit the alias matching for Chinese bundled fonts. That is practical guidance the schema does not convey, though the core matching rule is duplicated.

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 — searching the font catalog the cloud video renderer can load — and immediately scopes it (Google Fonts plus project-bundled custom fonts). It is clearly distinguishable from generic siblings like browse_assets or search_stock_media because it is explicitly about renderer-loadable fonts.

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?

Gives two concrete triggering conditions: an export reporting unsupported fonts, and picking fonts for motion-graphic items. That is strong when-to-use guidance with no ambiguity. It does not name a competing tool or state when not to use it, which keeps it short of a 5.

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

All ChatCut toolsInspect
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.

Resources