Skip to main content
Glama

add_revenue_entry

Add a new revenue opportunity to track bounties, grants, product sales, freelance gigs, or crypto earnings with details like amount, status, and deadlines.

Instructions

Track a new revenue opportunity (bounty, grant, product sale, freelance gig)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesRevenue source type
descriptionYesWhat is this opportunity
amount_usdYesDollar amount (honest estimate, not inflated)
statusNopending
urlNoLink to the opportunity
deadlineNoDeadline (ISO date)
notesNoAdditional notes

Implementation Reference

  • The handler implementation for 'add_revenue_entry', which reads the DB, creates a new entry with generated ID and submitted_at, and saves it.
    case "add_revenue_entry": {
      const db = loadDB();
      const entry: RevenueEntry = {
        id: generateId(),
        source: (args as any).source,
        description: (args as any).description,
        amount_usd: (args as any).amount_usd,
        status: (args as any).status || "pending",
        url: (args as any).url,
        deadline: (args as any).deadline,
        submitted_at: new Date().toISOString(),
        notes: (args as any).notes,
      };
      db.entries.push(entry);
      saveDB(db);
      return {
        content: [{ type: "text", text: `Added: ${entry.id} — ${entry.source} $${entry.amount_usd} (${entry.status})\n${entry.description}` }],
      };
  • The schema registration for 'add_revenue_entry', defining inputs like source, description, amount_usd, status, url, deadline, and notes.
    {
      name: "add_revenue_entry",
      description: "Track a new revenue opportunity (bounty, grant, product sale, freelance gig)",
      inputSchema: {
        type: "object" as const,
        required: ["source", "description", "amount_usd"],
        properties: {
          source: { type: "string", enum: ["bounty", "grant", "product", "freelance", "crypto"], description: "Revenue source type" },
          description: { type: "string", description: "What is this opportunity" },
          amount_usd: { type: "number", description: "Dollar amount (honest estimate, not inflated)" },
          status: { type: "string", enum: ["pending", "submitted", "approved", "paid", "rejected"], default: "pending" },
          url: { type: "string", description: "Link to the opportunity" },
          deadline: { type: "string", description: "Deadline (ISO date)" },
          notes: { type: "string", description: "Additional notes" },
        },
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. 'Track' implies persistence but does not disclose side effects, idempotency, lifecycle workflow implications, or what success/failure looks like for this 7-parameter mutation tool.

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?

Single sentence with efficient structure. Front-loaded with verb. Every word earns place, though extreme brevity may contribute to insufficient behavioral disclosure for a complex mutation tool.

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

Completeness2/5

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

Insufficient for a 7-parameter mutation tool with enum-based workflow state (status field) and no output schema. Missing: relationship to 'find_bounties' workflow, persistence guarantees, and return value description.

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 86% (high), establishing baseline 3. The parenthetical list '(bounty, grant...)' maps to enum values in the schema, adding marginal real-world context, but no parameter syntax or semantic relationships are explained beyond the schema itself.

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 uses a specific verb ('Track') and resource ('revenue opportunity'), and the parenthetical examples clarify scope. It implicitly distinguishes from sibling 'update_revenue_status' (add vs update), though 'Track' is slightly less precise than 'Create' or 'Add' for a mutation operation.

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?

No guidance provided on when to use this tool versus siblings like 'find_bounties' (discovery) or 'update_revenue_status' (modification). Does not mention workflow prerequisites or when NOT to use.

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