Skip to main content
Glama

weekly_report

Generate verified weekly revenue reports with accurate data for tracking opportunities like bounties, grants, and freelance gigs.

Instructions

Generate honest weekly revenue report — no inflated numbers, only verified data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the weekly_report tool which aggregates revenue data and PR statistics to generate a weekly report.
        case "weekly_report": {
          const db = loadDB();
          const prs = checkAllPRs();
          const now = new Date();
          const weekAgo = new Date(now.getTime() - 7 * 24 * 60 * 60 * 1000);
          const thisWeek = db.entries.filter(
            (e) => new Date(e.submitted_at || "").getTime() > weekAgo.getTime()
          );
    
          const report = `
    WEEKLY REVENUE REPORT — ${now.toISOString().slice(0, 10)}
    ============================================================
    
    LIFETIME:
      Total Earned: $${db.total_earned.toFixed(2)}
      Total Pending: $${db.total_pending.toFixed(2)}
      Total Entries: ${db.entries.length}
    
    THIS WEEK:
      New Entries: ${thisWeek.length}
      New Value: $${thisWeek.reduce((s, e) => s + e.amount_usd, 0).toFixed(2)}
      Paid: $${thisWeek.filter((e) => e.status === "paid").reduce((s, e) => s + e.amount_usd, 0).toFixed(2)}
    
    OPEN PRs: ${prs.length}
    PENDING BOUNTIES: ${db.entries.filter((e) => e.source === "bounty" && e.status === "submitted").length}
    PENDING GRANTS: ${db.entries.filter((e) => e.source === "grant" && e.status === "submitted").length}
    
    HONEST ASSESSMENT:
      - Only count PAID entries as revenue
      - Pending = not guaranteed
      - Scams filtered: ${db.scam_list.length} known scam repos
      - All numbers verified against real data
    `.trim();
    
          return { content: [{ type: "text", text: report }] };
        }
  • src/index.ts:364-367 (registration)
    Registration of the weekly_report tool within the server tool list.
      name: "weekly_report",
      description: "Generate honest weekly revenue report — no inflated numbers, only verified data",
      inputSchema: { type: "object" as const, properties: {} },
    },
Behavior3/5

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

With no annotations, description carries full burden. It adds valuable behavioral context that only 'verified data' is returned (not projections/unconfirmed entries), but lacks disclosure on return format, failure behavior, or side effects.

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?

Extremely concise single sentence with em-dash separation. Every word earns its place; 'honest' and 'verified' modify behavior while 'weekly' scopes the temporal range.

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 gaps remain: no output format description (PDF? JSON? text?), no mention of date range mechanics (current week? previous?), and no failure mode documentation.

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?

Zero parameters present, establishing baseline 4. No parameters requiring semantic clarification exist.

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?

Clear verb 'Generate' and resource 'weekly revenue report'. The 'honest' and 'verified data' qualifiers help distinguish from potentially unfiltered siblings like revenue_dashboard, though explicit differentiation is absent.

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 explicit guidance on when to use this versus revenue_dashboard or add_revenue_entry. No prerequisites or conditions mentioned.

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