Skip to main content
Glama

NoMac

by app.nomac
OverviewDiscussionsAdmin

Get Mac credit payment link

get_mac_checkout

Creates a checkout link for prepaid Mac credit, for the human to open and pay in their browser; it never charges anything itself. Credit comes in $10 packs (12.5 hours each), 1 to 10 per purchase, never expires, and bigger purchases earn bonus credit; the answer says what to suggest. The same request_key returns the same checkout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packsNoNumber of $10 packs, 1-10 (default 1), from the human's budget or expected hours
request_keyYesIdempotency key you choose (8-128 letters, digits and - _ . :). Repeat a lost call with the same key and arguments; a new key is new work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / packs / description
      Previous value: -"Number of $10 packs, 1-10. Pick from the human's stated budget or expected hours; 3+ packs earn bonus credit. Default 1."New value: +"Number of $10 packs, 1-10 (default 1), from the human's budget or expected hours"
    • changedInput schema / properties / request_key / description
      Previous value: -"Idempotency key you choose: 8-128 letters, digits, dashes, underscores, dots or colons. Retry a lost response with the same key and identical arguments; use a new key for new work."New value: +"Idempotency key you choose (8-128 letters, digits and - _ . :). Repeat a lost call with the same key and arguments; a new key is new work."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": {},
-  "description": "The JSON response of the NoMac API for this operation",
-  "properties": {
-    "error": {
-      "additionalProperties": {},
-      "description": "Present only when the call failed",
-      "properties": {
-        "code": {
-          "description": "Stable machine-readable error code, for example insufficient_credit",
-          "type": "string"
-        },
-        "message": {
-          "description": "What went wrong and what to do next",
-          "type": "string"
-        }
-      },
-      "required": [
-        "code",
-        "message"
-      ],
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / request_key / description
      Previous value: -"Idempotency key you choose (letters, digits, dash, underscore). Retry a lost response with the same key and identical arguments; use a new key for new work."New value: +"Idempotency key you choose: 8-128 letters, digits, dashes, underscores, dots or colons. Retry a lost response with the same key and identical arguments; use a new key for new work."
  4. Changed1 schema field changed
    • changedInput schema / properties / packs / description
      Previous value: -"Number of $10 packs, 1-10. Pick from the human's stated budget or expected hours; default 1."New value: +"Number of $10 packs, 1-10. Pick from the human's stated budget or expected hours; 3+ packs earn bonus credit. Default 1."
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the tool never charges anything itself, that credit comes in $10 packs (12.5 hours), never expires, and earns bonus credit at higher tiers, plus that the response 'says what to suggest'. The keyed idempotency statement ('the same request_key returns the same checkout') sits in mild tension with idempotentHint=false, though the description's 'a new key is new work' framing explains the annotation.

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 core action and side-effect disclaimer in the first clause, then packs constraints, pricing, and idempotency into a dense but readable single block. Slightly overstuffed — the pricing/tier detail is close to surplus for tool selection — but every sentence carries 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 2-parameter tool with no output schema, it covers the action, the side-effect boundary, the pricing model, idempotency, and hints at the response content ('the answer says what to suggest'). Remaining gaps are minor, e.g. checkout link lifetime or whether human presence is required.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds only marginal meaning over the schema (hours-per-pack and bonus context for 'packs'), while request_key semantics largely restate the schema.

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 concrete verb and resource: it 'Creates a checkout link for prepaid Mac credit', which usefully corrects the misleading 'get_' name and clarifies it 'never charges anything itself.' It does not explicitly name or route against siblings such as get_mac_credits or create_mac_link, so it stops short of full differentiation.

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 clear context for use: the link is 'for the human to open and pay in their browser', and it explains the purchase shape (1-10 packs per purchase). There are no exclusions or named alternatives, e.g. what to call when the human just wants to see an existing balance.

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

All NoMac toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources