Skip to main content
Glama

Assign job in CrewNest

crewnest_assign_job
Read-onlyIdempotent

Assign 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_assign_job"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The description adds genuinely useful behavior beyond the annotations: it explicitly says it 'returns how to do it step by step (screens, buttons, fields) and opens nothing by itself', which correctly reinforces readOnlyHint=true and warns the agent not to assume the job was actually assigned. The final sentence about CrewNest's official Job Pricing MCP server is unrelated to assigning jobs and dilutes rather than informs the behavioral picture.

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 purpose and the crucial 'opens nothing by itself' caveat are front-loaded and well ordered. But the closing sentence about an official Job Pricing MCP server with three read-only pricing tools has no bearing on assigning a job and reads as promotional padding that could mislead an agent into thinking price-calculation capability is relevant here.

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?

For a zero-parameter tool with no output schema, the description covers the essential contract: what comes back (step-by-step screens/buttons/fields), what it does not do (opens nothing), and how to complete the action via the browser tools. The main gap is the absence of any sibling routing guidance among the several assignment-related tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not attempt to explain what inputs the returned instructions will reference, but with an empty schema that is not a meaningful omission.

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 opening sentence names a specific verb and resource ('Assign job in the user's own CrewNest account'), and the following clause clarifies that the tool actually produces step-by-step instructions rather than performing the assignment. It does not distinguish itself from near-siblings such as crewnest_bulk_assign_jobs or crewnest_confirm_job_assignment, so an agent must still guess which of the assign-family tools to pick.

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?

It gives a clear follow-on path — 'then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser' — which tells the agent this is step one of a two-step workflow. However, there is no guidance on when to choose this over bulk assign, confirm assignment, or claim job, and no stated preconditions (e.g. which identifiers the user must supply before the guide is meaningful).

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