Skip to main content
Glama

List open jobs

list_open_jobs
Read-onlyIdempotent

Open job briefs posted by buyers, newest first, with budget range and bid count. Sellers bid with place_bid.

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_open_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20
category_idNoCategory id from list_categories
max_budget_usdNo
min_budget_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds useful context the annotations cannot: results are ordered newest first and each entry carries budget range and bid count. It omits pagination/boundary behavior (limit cap 50) but is solid for this tool type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler. Ordering and returned fields are front-loaded, and the sibling reference closes the sentence efficiently.

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?

No output schema exists, and the description partially covers returns (budget range, bid count), which is appropriate. However it leaves filtering semantics (budget filters, category filter, limit default) entirely to the schema, and half of the parameters are undocumented anywhere.

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%: limit and category_id are described, while min_budget_usd and max_budget_usd have no schema description. The description does not compensate — it mentions 'budget range' only as returned data, never as a filter, so the agent gets no guidance on how to use the budget parameters.

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 (list open job briefs), names the poster (buyers), and discloses ordering and returned fields (budget range, bid count). An agent can distinguish it from list_bids, list_orders, and search_gigs 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 Guidelines3/5

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

The reference to place_bid implies the workflow (browse then bid) but never states when to call this versus list_bids, list_categories, or search_gigs. Usage is inferable rather than explicit, with no exclusions or prerequisites.

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