get_fonts_cssGenerate ready-to-use @font-face CSS for a family spec (Google-Fonts-compatible), e.g. "inter:wght@400,700" or a variable range "inter:wght@300..900". Returns CSS text.
| Name | Required | Description | Default |
|---|---|---|---|
| family | Yes | Family spec, e.g. "inter:wght@400,700" or "inter:wght@300..900". | |
| display | No | font-display value (default swap). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent hints. The description adds that the tool returns CSS text and explains the family spec format, providing useful context beyond the annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, front-loaded sentence with examples and return type, no filler. Every element earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 2-param tool with read-only annotations, the description covers purpose, input format, and output type. Without an output schema, specifying 'Returns CSS text' provides adequate completion.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for both parameters. The description provides examples that mirror the schema descriptions, adding little new meaning. Baseline 3 is appropriate when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool generates @font-face CSS from a family spec, with specific verb 'Generate' and resource 'CSS'. It includes concrete examples distinguishing it from sibling tools that download fonts or files.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: it's for creating CSS-ready font-face rules from a Google-Fonts-compatible spec. However, it does not explicitly mention alternatives or when not to use this tool, though the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation within the color, font, or code utility domains. Descriptions clearly differentiate retrieval, search, and action tools, so an agent can reliably select the right one without ambiguity.
All names use snake_case and are readable, but there's a mix of direct verb_noun patterns (check_contrast, extract_colors) and a get_ prefix for retrieval tools (get_font, get_palette). The inconsistency is minor and the pattern remains predictable overall.
15 tools is at the upper end of the well-scoped range, but each tool serves a clear, distinct purpose across three focused domains (fonts, colors, code). No tool feels redundant or unnecessary for the server's mission.
The server provides a comprehensive lifecycle for its domains: font search, metadata, file access, CSS generation, and image recognition; color extraction, naming, shading, contrast checking, and palette search; and code detection, conversion, and minification. No obvious gaps exist.