Skip to main content
Glama
Sign In

Agentfonts

by com.agentfonts
OverviewDiscussionsAdmin

quote_license

Read-only

Price a licence (USD and USDC) and return machine-readable licence terms. Free, nothing is reserved.

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": {
      "use": "<use>"
    },
    "name": "quote_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
useYesLicence type. A foundry may define its own; get_family lists them
tierNoShorthand for the first dimension of the use (desktop: computers, web: visitors/month, app: apps, ebook: titles, server: cores)
font_idNoOne style. Or use font_ids or bundle_id.
optionsNoLicence dimensions, e.g. {"visitors": 100000, "domains": 2} or {"cores": 8, "years": 2}. get_family lists them per use.
font_idsNoSeveral styles of the same family, priced per style
bundle_idNoA family bundle from get_family, e.g. <family_id>.family

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real context beyond that: the operation is free and reserves nothing, so repeated calls have no commercial consequence. It stops short of describing response detail or any rate limiting, but for a read-only pricing call the key behavioral facts are covered.

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?

Two sentences, zero filler, with the action and output stated first and the no-commitment guarantee immediately after. Nothing could be removed without losing information.

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 six-parameter tool with a nested options object and no output schema, the description covers what the tool does, what it returns in general terms (pricing in two currencies plus machine-readable terms), and that it has no side effects. The main gap is the absence of any pointer to the quote-then-buy flow with its sibling, but the schema carries the parameter burden well.

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 100%, so use, tier, font_id/font_ids/bundle_id, and options are already fully explained in the schema, including the shorthand meaning of tier. The description adds no parameter-level meaning of its own, so baseline 3 applies.

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 ("Price a licence") and adds the output shape (USD and USDC, machine-readable licence terms). It does not name buy_license, but the phrase "nothing is reserved" implicitly separates it from a purchasing tool, so the purpose is clear 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 Guidelines3/5

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

"Free, nothing is reserved" signals this is a non-committal pricing step that can precede a purchase, which is useful implied guidance. However, it never explicitly says when to call this versus buy_license, or that a quote is a prerequisite for buying, leaving the agent to infer the workflow.

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

All Agentfonts 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