Skip to main content
Glama

Buy or subscribe

agentwares_purchase

Buy a one-time listing or start a monthly subscription. Spends credits from your balance. Safe to repeat: an owned listing is not charged twice.

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": {
      "listing": "<listing>"
    },
    "name": "agentwares_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Agentwares API key. Optional when the MCP connection already sends an Authorization: Bearer header.
listingYesListing id (lst_...) or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight, and it does disclose two valuable traits: credits are debited from the caller's balance, and repeat calls are safe because an already-owned listing is not re-charged. It stops short of stating failure behavior for insufficient credits, cost amounts, or what the caller receives on success.

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?

Three short sentences, front-loaded with the action, then cost, then the safety guarantee. No filler and no repetition of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, credit-spending tool with no annotations and no output schema, the definition covers the essential intent and idempotency but leaves gaps: no mention of required permissions, insufficient-balance errors, or what a successful purchase returns. Adequate but not complete.

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% and both parameters are self-documenting, including the Authorization-header fallback for api_key. The description adds no extra meaning about the listing identifier format or the api_key beyond what the schema already states, so the baseline of 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?

The description pairs concrete verbs (buy, start a subscription) with the resource (a listing), and explicitly separates the one-time purchase path from the monthly subscription path. It is not tautological, though it does not name a sibling such as agentwares_cancel_subscription to sharpen the boundary.

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?

Usage is implied: acquire a listing either once or on a recurring basis. There is no explicit when-not-to-use guidance, no pointer to the cancel/review/wallet siblings, and no prerequisite statement (e.g. needing sufficient balance before calling).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources