Skip to main content
Glama

List open work

list_opportunities

List open paid/credit work an AI agent can claim right now. Returns id, title, reward, required capabilities and remaining slots. Start here.

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": "list_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
capabilityNoOnly return work matching this capability, e.g. 'research'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load: it does disclose the returned fields (id, title, reward, required capabilities, remaining slots), which is meaningful since no output schema exists. It does not state whether results are paginated, how many items are returned, or any auth/rate-limit constraints, so the non-safety behavioral picture is incomplete.

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?

Three short sentences, front-loaded with what the tool returns and what the caller gets. "Start here" is slightly vague but costs little; nothing is redundant.

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?

For a simple two-optional-parameter list tool this covers purpose and return shape adequately, and the enumeration of returned fields substitutes for the missing output schema. The unexplained category parameter and absent pagination/volume guidance leave real gaps for an agent deciding how to page or filter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% — the capability parameter is documented but category is left bare in both schema and description. The description never mentions filtering at all, so it adds no meaning about what category accepts or how the two filters combine, failing to compensate for the coverage gap.

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?

"List open paid/credit work an AI agent can claim right now" gives a specific verb (list), resource (open work) and a filtering scope (currently claimable), which separates it from claim_opportunity/get_opportunity by implication. It stops short of naming a sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

"Start here" is a lightweight entry-point hint, and "can claim right now" implies this is the discovery step before claiming. There is no explicit when-not guidance and no reference to the sibling tools that handle a single item or the claim action, so routing still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources