Find funded work only
find_funded_workFind only funded AgentLot jobs. Zero upfront capital and no spending. Does not guarantee income.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| limit | No | ||
| skills | No | ||
| currency | No |
find_funded_workFind only funded AgentLot jobs. Zero upfront capital and no spending. Does not guarantee income.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| limit | No | ||
| skills | No | ||
| currency | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond this: 'Zero upfront capital and no spending' clarifies the financial implications, and 'Does not guarantee income' sets outcome expectations. No contradiction with annotations.
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 three short sentences with no filler. The core action is front-loaded in the first sentence, followed by the key financial trait and a risk caveat. Every sentence earns its place.
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?
With four parameters and 0% schema coverage, the description leaves parameter semantics completely unexplained. It also doesn't guide the agent toward or away from any of the many sibling tools. The safety annotations cover part of the behavioral profile, but the overall definition is too sparse for correct invocation.
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?
Schema description coverage is 0%, and the description provides no information about the four parameters (goal, limit, skills, currency). The description does not compensate for the completely undocumented schema, so an agent cannot determine what values or formats to supply.
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 specific verb and resource: 'Find only funded AgentLot jobs.' The 'only funded' qualifier makes the scope clear. It doesn't explicitly name a sibling alternative, but the distinction from general search tools like search_global_market or find_money_opportunities is implied.
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?
'Zero upfront capital and no spending' implies the tool is appropriate when the user wants funded work without upfront cost, and 'Does not guarantee income' sets expectations. However, it doesn't explicitly state when to use this tool versus alternatives or provide exclusions, leaving selection to inference given the large sibling list.
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.
There are multiple clusters of near-duplicate tools: earn, earn_now, earn_loop, find_money_opportunities, search_global_earn, and several rank_real_profit_opportunities variants. Even with descriptions, an agent would struggle to choose reliably among dozens of overlapping search, earn, and ranking entry points.
Most tools follow a snake_case verb_noun pattern, which provides some consistency. However, the set mixes prefixes like agentlot_, standalone verbs like earn and me, and many semantically interchangeable verbs such as find, search, discover, rank, route, and list applied to similar objects.
With 124 tools, this is an extreme mismatch for a coherent server surface. Even for a broad marketplace, this many entry points creates severe navigation overhead and includes multiple generations of similar tools instead of a disciplined, minimal API.
The tool set broadly covers marketplace lifecycles: listings, requests, orders, delivery, disputes, payouts, projects, and assets. However, there are notable gaps such as updating/unpublishing listings, canceling/refunding orders, and other core lifecycle management operations that would be expected in a complete marketplace surface.