Skip to main content
Glama

Confirm job assignment in CrewNest

crewnest_confirm_job_assignment
Read-onlyIdempotent

Confirm job assignment 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_confirm_job_assignment"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself' and by describing the return as a step sequence. What it adds beyond the annotations — that this is a guidance/instruction tool and that a separate browser toolset performs the actual action — is genuinely useful. The final sentence about CrewNest's official Job Pricing MCP server is unrelated to this tool's behavior and dilutes rather than informs.

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 'returns steps, opens nothing' clarification are front-loaded, which is good. But the closing sentence about CrewNest's official free Job Pricing MCP server is off-topic marketing copy for a different capability and does not earn its place in this definition.

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 zero parameters, no output schema and rich annotations, the remaining burden is explaining what the tool returns — and it does, naming 'screens, buttons, fields' and the follow-up browser tools. An agent can call it and know what to do with the result. The only gap is the missing link to the direct-action siblings for the case where the user does not want a guided walkthrough.

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 the description carries no parameter-semantics burden and baseline 4 applies. No parameter meaning is missing because there is nothing to call with.

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 states a concrete resource (job assignment in the user's CrewNest account) and then clarifies the actual mechanic: it returns step-by-step instructions (screens, buttons, fields) rather than performing the confirmation. That correctly disambiguates it from the action-performing siblings like crewnest_assign_job, but it never names such a sibling explicitly, so it falls short of a 5.

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 implied workflow guidance: call this to get the steps, then execute them with the cotlet_browser_* tools in the CrewNest Cloud Browser. However, it never states when to prefer this guided path over a direct-crew operation such as crewnest_assign_job, nor any precondition (e.g., an existing assignment that needs confirming). The usage context is inferable but not explicit.

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