Skip to main content
Glama

Set technician visibility in CrewNest

crewnest_set_technician_visibility
Read-onlyIdempotent

Set technician visibility 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_set_technician_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds the critical behavioral fact those hints cannot convey: this tool opens nothing by itself and only returns instructions (screens, buttons, fields). An agent knows exactly what side effects to expect and what the follow-up step is.

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 is two well-ordered sentences that front-load the purpose and the handoff. However, the trailing sentence about CrewNest's official Job Pricing MCP server and its read-only pricing tools is unrelated to setting technician visibility and reads as promotional noise that an agent must filter out.

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 guidance tool with no output schema, the description covers what is returned (step-by-step UI instructions) and how to act on it. Minor gaps remain, such as whether the steps are plain text and any account prerequisites, but an agent has enough to invoke it correctly.

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 and the baseline of 4 applies. The description adds no parameter detail, which is appropriate here since the schema is empty.

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 specific resource (technician visibility in the user's CrewNest account) and, crucially, clarifies the actual mechanism: it returns step-by-step instructions rather than performing the change. That distinction is what an agent most needs. It does not explicitly contrast with sibling tools like crewnest_list_crew, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear operational context: run this first to get the steps, then perform the action with cotlet_browser_* tools in the user's CrewNest Cloud Browser. The workflow handoff is explicit. It stops short of stating when-not-to-use or naming a non-browser alternative, so it is not a 5.

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