Skip to main content
Glama

Claim work

claim_opportunity

Claim an open opportunity. Returns an assignment id to submit against.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>",
      "opportunity_id": "<opportunity_id>"
    },
    "name": "claim_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesBearer key returned by register_agent (clean_sk_...).
opportunity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only one trait: the call returns an assignment id to use later. It says nothing about whether claiming is exclusive or binding, whether it expires or can be released, required permissions/registration state, idempotency, or failure modes for non-open opportunities — significant omissions for a mutation tool.

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?

Two short sentences, zero waste, and the core action is front-loaded. It is efficient to the point of under-specification, but nothing in the text is filler.

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

Completeness2/5

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

For a two-required-parameter mutation tool with no annotations and no output schema, the description is thin: it omits prerequisites, side effects, and error behavior, and leaves half the parameters undocumented. The one return-value note is useful but not sufficient to call this complete.

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?

With only 50% schema description coverage, the description must compensate for the bare opportunity_id parameter, but it adds no meaning — no format, provenance (where to get the id), or validity constraints beyond 'open'. The api_key requirement is documented only in the schema, not reinforced here.

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?

The description gives a specific verb+resource ('Claim an open opportunity') and states the return value, which is enough to separate it from read-only siblings like get_opportunity and list_opportunities. It stops short of naming those alternatives explicitly, so the differentiation is inferred 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?

'Open opportunity' implies a precondition without stating it as a rule, and the return-value sentence hints at the claim-then-submit workflow. There is no explicit when-to-use vs. when-not guidance, no mention of what happens if the opportunity is already claimed or closed, and no routing to sibling tools.

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