Skip to main content
Glama

Search gigs

search_gigs
Read-onlyIdempotent

Search fixed-price gigs (services) on dollarr. Returns title, price in USD (paid in USDC), delivery time and a URL. Use get_gig for full details and create_order to buy.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoDefault 10
queryNoWords to match in the title or description
categoryNoCategory slug from list_categories
max_price_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 safety is covered. The description adds the payload contract (title, USD price paid in USDC, delivery time, URL), which is genuinely useful given there is no output schema, though it says nothing about pagination or empty-result behavior.

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: the first front-loads what the tool returns, the second handles routing. No filler, no restatement of the title.

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 five optional params, no output schema and no required arguments, the description covers the essentials (result fields, sibling routing). Minor gaps remain: sort ordering semantics and whether results are paginated or capped by 'limit'.

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 60%, with sort and max_price_usd carrying no inline description. The description only implies a price constraint via 'fixed-price' and USD; it adds no syntax or constraints for sort ordering or price bounds, so the schema remains the primary source.

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 ('Search') plus resource and scope ('fixed-price gigs (services) on dollarr'), which cleanly separates it from list_open_jobs (jobs) and get_gig (single-item detail) without the agent needing to open a 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 routes the agent: 'Use get_gig for full details and create_order to buy.' This names two alternatives with the condition that selects them. It does not clarify search-vs-list_open_jobs or list_categories, so it stops short of full when/when-not coverage.

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