Find open jobs in the marketplace that need providers, with optional filters for token, amount, and result limit.
Browse available jobs in the marketplace that need providers. No api_key required.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20) | |
| token | No | Filter by token symbol (optional) | |
| max_amount | No | Maximum job amount (optional) | |
| min_amount | No | Minimum job amount (optional) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose all behavioral traits. It only states no API key needed. It omits important details like pagination, sorting, default limit, and return format, leaving the agent uncertain about the tool's behavior.
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 extremely concise, with only two sentences that convey the core purpose and a key usage note. No filler or redundant information.
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?
Given the tool's simplicity (4 optional params, no output schema) and lack of annotations, the description is adequate but minimal. It could be more complete by mentioning default limit or response structure, especially since similar sibling tools exist.
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 100%, so the baseline is 3. The description adds no extra parameter context beyond what the schema already provides, such as clarifying the meaning of 'token' or the range of amounts.
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 clearly states it browses available jobs needing providers, making the purpose obvious. However, it does not distinguish from similar sibling tools like browse_jobs_with_economics or find_matching_jobs, which could cause confusion.
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?
The description mentions 'No api_key required,' giving a minor guideline, but provides no comparison or when-not-to-use instructions. With siblings like find_matching_jobs and browse_jobs_with_economics, the agent gets no guidance on selecting this tool over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.