Skip to main content
Glama
ElromEvedElElyon

revenue-mcp

by ElromEvedElElyon
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

product_catalog

List all products and track their monetization status to identify revenue opportunities and monitor deadlines.

Instructions

List all products and their monetization status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:532-549 (handler)
    Handler implementation for the product_catalog tool, which returns a static list of products and their details.
    case "product_catalog": {
  const products = [
    { name: "claw-mcp-toolkit", type: "Open Source MCP", price: "Free (MIT)", status: "LIVE", url: "github.com/ElromEvedElElyon/claw-mcp-toolkit", revenue: "Sponsorship / Consulting" },
    { name: "ClawChat Pro v1.0", type: "AI Chat SaaS", price: "$9.99/mo", status: "LIVE on sintex.ai", revenue: "Stripe subscription" },
    { name: "SintexOS", type: "AI Operating System", price: "$29.99", status: "LIVE on sintex.ai", revenue: "One-time purchase" },
    { name: "Zero to $1M Book", type: "Digital Book", price: "$9.99", status: "WRITTEN (175K words)", revenue: "Gumroad / Amazon KDP" },
    { name: "FLASH Payment System", type: "Payment Infrastructure", price: "Enterprise", status: "BUILT (99 tests)", revenue: "Licensing / SaaS" },
    { name: "bUSD1 (BITCOIN•USD•ONE)", type: "Runes Stablecoin", price: "Peg: $1.00", status: "ETCHED (0 mints)", revenue: "Mint fees + DeFi" },
    { name: "STBTCx", type: "Solana Token", price: "Market", status: "LAUNCHED (not graduated)", revenue: "Trading / LP" },
    { name: "revenue-mcp", type: "Revenue Intelligence MCP", price: "Free (MIT)", status: "NEW", revenue: "Consulting / Premium features" },
  ];
  return {
    content: [{
      type: "text",
      text: `PRODUCT CATALOG (${products.length} products):\n\n${products.map((p) => `${p.name}\n  Type: ${p.type} | Price: ${p.price}\n  Status: ${p.status}\n  Revenue: ${p.revenue}`).join("\n\n")}`,
    }],
  };
}
  • src/index.ts:358-362 (registration)
    Registration of the product_catalog tool within the server tool definition array.
    {
  name: "product_catalog",
  description: "List all products and their monetization status",
  inputSchema: { type: "object" as const, properties: {} },
},

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

Implies read-only operation via 'List' and indicates unfiltered scope with 'all', which partially compensates for missing annotations. However, fails to disclose return format, pagination behavior, or authentication requirements given zero annotation coverage.

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?

Single front-loaded sentence with zero waste. Begins with action verb and efficiently communicates both the resource and the specific data attribute returned.

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?

Adequate for a zero-parameter tool but falls short given lack of output schema and annotations. Description omits return value structure, pagination limits, and cache behavior necessary for agent planning.

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?

Input schema contains zero parameters, warranting baseline score per guidelines. Description correctly implies no filtering capabilities are available by stating 'all products', aligning with the empty 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 specific verb 'List' and resource 'products' plus specific attribute 'monetization status'. Implies distinction from sibling 'revenue_dashboard' (aggregation vs catalog) and 'update_revenue_status' (read vs write), though does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this versus siblings like 'revenue_dashboard' or 'find_bounties'. Lacks prerequisites, scoping constraints, or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ElromEvedElElyon/revenue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server