Skip to main content
Glama

Marginrule pricing agent

List platforms and fee presets

list_platforms
Read-onlyIdempotent

Every platform and plan this server knows (Etsy, Shopify Basic, Payhip Free/Plus/Pro, Gumroad direct/Discover, Ko-fi Shop, Notion Marketplace, Square online/in person) with its rates as fractions, fixed and listing fees in USD, monthly plan fee, whether it sells digital downloads, whether the seller adds their own processor, the tax-base flag, fees-as-of date and source URLs. Also the card processor presets. Call this first to get valid platform ids.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 safety is covered. The description adds genuinely useful context beyond that: data provenance via a 'fees-as-of date' and source URLs, and the inclusion of card processor presets, which tells the agent how much to trust the returned rates.

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?

Front-loaded with the scope ('Every platform and plan this server knows') followed by the enumerated contents and a short action directive. The long parenthetical earns its length by letting the agent know whether its platform of interest is covered without making a call.

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 and no parameters, the description carries the full burden of saying what comes back, and it does so field by field (rates as fractions, fixed/listing fees in USD, monthly plan fee, digital-download support, own-processor flag, tax-base flag, date, sources). An agent has enough to decide to call it and to interpret the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the text misleads about inputs.

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 (list every platform and plan this server knows) and then enumerates the concrete platforms and the per-platform facts returned. The closing 'Call this first to get valid platform ids' makes its role as the reference/lookup tool distinct from the fee-calculation siblings.

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 says to call this first to obtain valid platform ids, which is clear prerequisite guidance for any follow-up call. It does not name a when-not-to-use case or name a sibling alternative, so it stops short of full routing guidance.

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