Skip to main content
Glama

Transfer business ownership in CrewNest

crewnest_transfer_business_ownership
Read-onlyIdempotent

Transfer business ownership 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_transfer_business_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', so there is no contradiction and the agent gets confirmation that the ownership transfer is not actually executed here. It also discloses the return shape (screens, buttons, fields), which is useful behavior beyond the annotations, though it says nothing about prerequisites such as owner/admin role.

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 core two clauses are front-loaded and efficient, but the final sentence about CrewNest's official Job Pricing MCP server is off-topic for this tool and dilutes focus. Removing it would tighten the definition considerably.

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 no output schema, the description takes on the job of explaining the return value (step-by-step screens/buttons/fields), which it does adequately, and it clarifies that the follow-up action happens in the browser tools. The unrelated API-promo sentence is the main incompleteness/inconsistency in an otherwise sufficient definition.

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?

There are zero input parameters, so the baseline is 4, but the description adds nothing about whether the account or user is inferred from context. A one-line note on whose account is targeted would have earned a higher mark.

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?

Names a specific verb and resource (transfer business ownership in CrewNest) and disambiguates the misleading name by stating it returns step-by-step instructions and 'opens nothing by itself'. It does not name any sibling tool to differentiate from, and the first sentence reads initially as if the tool performs the transfer, creating brief ambiguity.

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 forward path — read the returned steps, then act via the cotlet_browser_* tools in the Cloud Browser — which is real usage context. However, there is no explicit when-not guidance and the closing note about CrewNest's Job Pricing MCP server is unrelated to when to call this tool, adding noise rather than routing help.

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