Skip to main content
Glama

Claim job in CrewNest

crewnest_claim_job
Read-onlyIdempotent

Claim job in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds the non-obvious workflow fact that this tool only emits instructions and requires a browser tool to actually perform the claim. That is meaningful context beyond the structured fields. It loses a point for not saying what the response looks like in practice or what happens when no matching job exists.

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

Conciseness3/5

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

The first two sentences are front-loaded and earn their place, stating purpose then the two-step workflow. The third sentence about CrewNest's 'official, free Job Pricing MCP server with three read-only tools' is unrelated to invoking this tool and is pure noise that dilutes the signal.

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 zero-parameter, read-only guidance tool with no output schema, the description covers the essential mechanism (returns steps, does not act) and the follow-up path (cotlet_browser_* tools). It is incomplete on job identification, on what the returned steps contain structurally, and on failure modes, while spending its final sentence on off-topic promotion.

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?

With zero parameters the baseline is 4, but the definition never addresses the obvious question an agent will have: if this tool claims a specific job, how is that job identified without any job ID or selector? The description leaves that to be inferred from the browser session context rather than stating it.

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 makes the real behavior explicit: it returns step-by-step CrewNest instructions (screens, buttons, fields) and "opens nothing by itself," which resolves the tension between the verb 'Claim' in the name and the read-only nature of the tool. It also names the sibling family that actually performs the action (cotlet_browser_*), so an agent can distinguish this planning/guidance tool from the execution tools. It stops short of a 5 because the opening sentence ('Claim job in the user's own CrewNest account') still reads like a mutation and could mislead on first pass.

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?

There is one genuinely useful routing instruction: call this first, then execute with cotlet_browser_* in the user's CrewNest Cloud Browser. However, there is no guidance on when not to use it, no mention of how it relates to the many job-mutation siblings (assign_job, update_job_status, confirm_job_assignment), and the final sentence about a separate Job Pricing MCP server is unrelated advertising that adds no selection guidance.

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