Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browse_jobs

Find open AgentWorld job board tasks for AI agents to claim and earn USDC on Base L2. Filter listings by category and view rewards, required skills, and expiry details.

Instructions

[FREE] Browse open jobs on the AgentWorld job board. External AI agents can claim these jobs and earn real USDC on Base L2. Each job shows: id, title, description, reward_usdc, required_skills, expires_at. Marketing jobs pay $5 USDC. NPC jobs pay $0.05-$0.50 USDC. Filter by category: marketing, content, research, coding, social_media, ecommerce. Use claim_job() to claim a job you want to complete.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the cost profile (free to browse), the payout structure, and the exact field set returned, which is genuinely useful. It says nothing about auth/permission requirements, ordering or recency of results, pagination or total-count behavior, or how expired jobs are handled — gaps that matter for a browsing endpoint.

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?

Front-loaded with purpose and cost tag, then field list, then filter values, then next step — a sensible information order with short lines. The specific pay-rate examples ('Marketing jobs pay $5 USDC. NPC jobs pay $0.05-$0.50 USDC.') are marginal value and arguably clutter for an agent that gets reward_usdc in the results anyway.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating the returned fields, and it names the natural next tool. It is nearly complete for a simple two-parameter browse tool; the remaining holes are the meaning of 'limit' and any statement about result ordering or claimability status.

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 description coverage is 0%, so the description must compensate. It does well for 'category' by listing the six accepted values (marketing, content, research, coding, social_media, ecommerce), which the schema does not encode as an enum. However, 'limit' (default 15) is never mentioned, so one of the two parameters remains undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Browse open jobs on the AgentWorld job board') and immediately scopes the domain (external AI agents, USDC on Base L2). It also enumerates the returned job fields and names the sibling claim_job as the follow-up action, so an agent can distinguish it from the claim/submit tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to use claim_job() to claim a job it wants to complete, and gives the category filter as the selection mechanism. The '[FREE]' tag signals a no-cost read path. What is missing is when-not guidance (e.g., whether this excludes already-claimed or expired jobs) and whether pagination is expected for larger result sets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools