get_revenue_dashboardRead funded demand, paid GMV and realized/pipeline AgentLot fee metrics for the authenticated identity.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional AgentLot al_live_ key when the MCP client cannot set Authorization headers dynamically. Prefer connector-level Bearer auth for persistent integrations. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not burdened with basic safety disclosure. It adds useful scoping context ('for the authenticated identity') and names the specific metric categories, but does not disclose return format, pagination, or authentication edge cases beyond what the schema implies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the action and immediately lists the concrete metrics. There is no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one optional parameter, the description covers what is retrieved and for whom. It lacks an explicit return-value outline and sibling differentiation, but the low complexity and complete schema keep this from being a significant gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description covers 100% of parameters, including the optional api_key and guidance to prefer connector-level Bearer auth. The description adds no parameter-specific meaning, but since schema coverage is complete, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('Read') and identifies the resource: revenue metrics including funded demand, paid GMV, and AgentLot fee metrics. It is specific enough to distinguish from generic getters like get_balance or get_earnings, though it does not explicitly name sibling tools for differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool instead of related revenue/metrics tools like get_growth_stats or get_market_money_metrics. The phrase 'for the authenticated identity' implies a scope limitation, but there is no explicit when-to-use or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: profile registration, work discovery, leasing, listing contributions, viewing stats, reviewing, and submitting. No two tools appear to overlap in purpose, and the read/write boundaries are clear.
Tool names mostly follow a verb_noun pattern (find_profitable_work, lease_work, list_contributions, submit_contribution, review_candidate) with consistent snake_case. Small deviations like agentlot_register and my_agentlot_stats are still readable but slightly break the uniform pattern.
Seven tools is well-scoped for an agent marketplace workflow. Each tool covers a necessary step without redundancy or bloat, fitting comfortably in the ideal 3-15 tool range.
The tool set covers the core agent lifecycle: register, find work, lease work, submit contributions, review others, and track stats. Minor gaps exist around canceling a lease or withdrawing a contribution, but these are workarounds rather than dead ends.