Skip to main content
Glama
Sign In

Agoranome seller tools

by io.github.Agoranome
OverviewDiscussionsAdmin

Agent payments weekly (free)

agent_payments_weekly
Read-only

Free: Agoranome Weekly's edition for a week (the newest if week is left out): real demand on Base (payments into the busiest Bazaar sellers with catalog sweeps and self-payments taken out), the Bazaar's sellers, new sellers, price index and Fair Offer share, and x402 SDK downloads, with the method version and how to cite it. CC BY 4.0.

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

Input Schema

NameRequiredDescriptionDefault
weekNoISO week, e.g. 2026-W44

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only/open-world, so the description correctly spends its words elsewhere: it flags the free tier, the null-week fallback, the inclusion of the method version and citation instructions, and the CC BY 4.0 license. Rate limits and freshness lag relative to 'now' are not stated.

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?

A single front-loaded sentence that opens with the free tier and the resource, then lists payload contents; there is no filler. It is dense and heavily parenthesized, which costs a little readability but not correctness.

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?

With no output schema, one optional parameter, and annotations covering safety, the description does the work that matters: it enumerates the returned metrics and mentions the method version and citation. Only the relationship to weekly_insights and data freshness remain uncovered.

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?

Schema coverage is 100% and the schema already documents the ISO-week format, so the baseline is 3. The description earns one more by explaining what the schema only implies: that omitting week yields the newest edition rather than an error or empty result.

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 resource (Agoranome Weekly's edition for a given week) and enumerates its contents — demand on Base, sellers, price index, Fair Offer share, x402 SDK downloads. An agent can tell what data comes back, though the jargon ('Bazaar', 'Fair Offer share') is unexplained and the closely-named sibling weekly_insights is never referenced.

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?

The only usage rule given is the default behavior — 'the newest if week is left out' — which is genuinely useful. There is no statement of when to choose this over weekly_insights or any other sibling, and no prerequisites or exclusions are named.

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

All Agoranome seller tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources