Kódvéna

Ingyenes betűtípusok keresése

search_free_fonts

Read-onlyIdempotent

Keresés a Kódvéna ingyenes betű-adatbázisában: 135 kurált, ingyenes (OFL-1.1 / Apache-2.0) betűcsalád, mindegyikben magyar ő és ű. Név, stílus (pl. elegáns, geometrikus, kerekített) vagy leírás szerint, kategóriaszűrővel; minden találathoz súlyok, licenc, párosítási tipp és link az előnézethez, a @font-face kódhoz és a ZIP-letöltéshez.

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": "search_free_fonts"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Keresőszó(k), pl. „elegáns”, „montserrat”, „kerekített”
`category`	No	sans (talpatlan), serif (talpas), display (díszbetű), kezi (kézírás), mono (monospace)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: the license types, the guaranteed Hungarian diacritic coverage, and exactly what each hit returns (weights, license, pairing tips, preview/@font-face/ZIP links).

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?

A single dense sentence, but it is front-loaded with the core purpose and every clause (licenses, diacritics, query modes, result contents) carries information. Slightly long, yet nothing is filler.

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?

With no output schema, the description takes on the burden of describing return values and does so thoroughly (weights, license, pairing tips, preview and download links). Combined with the annotation coverage, an agent has everything needed to call and interpret it.

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 67% and the description meaningfully extends it by clarifying that 'query' accepts a font name, a style adjective, or free description, and that 'category' acts as a filter. The 'limit' parameter is left unexplained, which keeps it from a 5.

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 ('Keresés a Kódvéna ingyenes betű-adatbázisában') and pins down scope: 135 curated OFL-1.1/Apache-2.0 families with Hungarian ő/ű support. An agent can immediately tell this apart from search_icons or generic search.

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?

Explains the three query modes (name, style, description) and the category filter, which gives clear context for how to call it. It stops short of naming when to prefer a sibling tool or any exclusions, so it is not a full when/when-not statement.

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

All Kódvéna 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.

Resources

Need Help?