Skip to main content
Glama
Sign In

Agoranome seller tools

by io.github.Agoranome
OverviewDiscussionsAdmin

Weekly x402 insights, by the page

insights_page
Read-only

One page of the weekly x402 demand insights report for $0.05, where the whole report is $0.25: repeat demand by category, demand gaps, movers, the price index with the listings that changed price, strong listings with weak descriptions, or GET against POST. Every metric of that page as JSON with Markdown, and its cited sources, for the latest or any archived week. The contents are free at /contents. Price: $0.05 in USDC per call, paid with x402 inside the tool call. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.05 to it. Failed calls aren't charged.

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": {
      "page": "<page>"
    },
    "name": "insights_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesWhich page. category_demand: Where repeat demand is: each category's repeat calls, share, busiest listing and leaders. demand_gaps: Demand gaps: categories with real repeat demand and few strong sellers. movers: Movers: listings that gained payers, new listings with traction, and drop-outs. price_index: Price index: points by category, and the listings that cut or raised their price. thin_leaders: Strong listings with weak descriptions. method_traction: GET versus POST: how often each reaches 3+ payers.
weekNoISO week, as 2026-W45; the latest if omitted
kyapay-tokenNoA Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already say readOnly and openWorld, so the description earns credit for the payment model: $0.05 in USDC via x402 inside the call, or a Skyfire/kya-pay token via header or argument, plus 'failed calls aren't charged'. That is real operational context an agent cannot get from annotations. It doesn't mention rate limits or latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and price are front-loaded, which is good, but the payment sentence is dense and repeats the $0.05 price already stated in the first clause, and the page list duplicates the enum. It is informative but carries avoidable redundancy and long compound sentences.

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, the description compensates by saying the tool returns every metric of that page as JSON with Markdown plus cited sources. Combined with the payment and week scope, an agent has everything needed to call it correctly.

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 the page enum already documents all six values in detail, so the description's paraphrase of the page list adds little. It does clarify that week accepts the latest or any archived week, but the schema's week description already says the same.

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 verb and resource: fetch one page of the weekly x402 demand insights report, with the page domain listed (repeat demand by category, demand gaps, movers, price index, thin listings, GET vs POST). It implicitly separates itself from weekly_insights by saying 'one page' versus 'the whole report is $0.25', but never names the sibling.

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?

Clear framing of when to use it: when you want a single page rather than the $0.25 whole report, and the note that contents are free at /contents tells the agent a non-paid alternative exists. It stops short of naming weekly_insights explicitly as the bulk alternative.

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