Skip to main content
Glama

Macfax

by com.macfax

Check Macfax resolution credits

get_macfax_credit_balance
Read-onlyIdempotent

How many serial resolutions this API key has left, and what actually costs a credit. Only a brand new resolution is billed: a 2021+ (10 character) serial Macfax has never resolved and that this key has not looked up in the last 24 hours. Cached serials, pre-2021 serials, repeats within 24 hours and every other tool are free at every tier. Call this before a large batch of serials to find out whether it can be finished. Without a key it reports the anonymous allowance instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the exact billing rule (2021+ serial, never resolved, not looked up in 24h), free categories, and anonymous allowance fallback, giving full behavioral transparency.

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?

Four sentences pack essential information: credit count, billing rule, usage advice, and anonymous fallback. No redundancy, but slightly longer than necessary; still well-structured and front-loaded.

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?

Given zero params and no output schema, the description provides sufficient context on output (remaining credits), when to use, and edge cases (anonymous allowance). The credit policy detail makes it fully self-contained for an agent.

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?

Tool has no parameters; schema coverage is 100% vacuous. Baseline of 4 is appropriate, and description adds context about API key vs anonymous allowance, though no parameter syntax needed.

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?

The description clearly states the tool reports remaining serial resolutions for the API key and explains what constitutes a billable resolution, distinguishing it from sibling lookup and listing tools.

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?

Explicitly instructs to call before a large batch of serials to determine feasibility, and clarifies that other tools are free, implying no need for credit checks elsewhere. Does not name specific alternatives but provides clear context.

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

All Macfax toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct function: checking listing trust, creating alerts, fetching price stats, retrieving reports, serial lookup, and searching listings. No overlap.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (check, create, get, get, lookup, search) with clear, descriptive names.

Tool Count5/5

6 tools cover the core domain of used Mac market info without being excessive or insufficient.

Completeness4/5

Covers search, trust check, pricing, reports, serial identification, and alerts. Minor gap: no tool to list or delete alerts, but core workflows are supported.

Resources