Skip to main content
Glama

Manage service address in CrewNest

crewnest_manage_service_address
Read-onlyIdempotent

Manage service address 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_manage_service_address"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotent, and closed-world, and the description is consistent with them by saying it 'opens nothing by itself.' It adds genuinely useful context beyond the annotations: the return is human-readable procedural instructions (screens, buttons, fields) and there is a required follow-up tool family. No detail on length or failure modes, so not a 5.

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, but the final sentence about CrewNest's official Job Pricing MCP server is unrelated to this tool and adds noise an agent must filter. 'from ChatGPT, Claude or any AI agent' is also filler.

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 parameterless, annotation-backed guidance tool with no output schema, the description covers what it returns and how to act on it. The only deficit is the distracting third-party-API sentence, which doesn't impair correct invocation but weakens focus.

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 baseline is 4; the description adds nothing to parameterize and nothing is missing. It does not explain that the target address is inferred from account context, which would have been a helpful note.

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?

States the resource (service address in the user's CrewNest account) and, crucially, that the tool itself returns step-by-step instructions rather than performing the change. 'Manage' is still ambiguous about whether it covers creating, editing, or removing an address, and no sibling is named, but the guidance-vs-action distinction is clear enough to select it correctly.

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?

Gives explicit workflow routing: call this to get the CrewNest steps, then execute them with the cotlet_browser_* tools in the Cloud Browser. It does not name an alternative when the agent already knows the steps or when the user wants a different service field, so it falls short of full when/when-not coverage.

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