Skip to main content
Glama

Manage subscription in CrewNest

crewnest_manage_subscription
Read-onlyIdempotent

Manage subscription 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_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, and the description is consistent with that by stating "opens nothing by itself" and describing the instruction payload. That said, the final sentence about CrewNest's separate Job Pricing MCP server is unrelated to this tool and adds noise rather than behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two clauses are efficiently front-loaded and explain the core behavior. The third sentence about an unrelated Job Pricing MCP server wastes space and could mislead an agent about the tool's scope, and the phrase "from ChatGPT, Claude or any AI agent" is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 safety annotations and no output schema, the description covers what it returns (screens, buttons, fields) and how to act on it (browser tools). Completeness is dragged down by the off-topic official-API sentence, which leaves no clear guidance on the operation scope it supports.

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 with 100% schema coverage, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool is 4, and the description avoids inventing parameter confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and resource ("Manage subscription") and usefully clarifies that the tool returns step-by-step UI instructions rather than performing the action. However, "manage" is operationally vague — it doesn't say whether it covers upgrading, cancelling, or changing plans — and it never explicitly contrasts with the sibling crewnest_get_subscription. An agent can infer this is a guidance tool, but not clearly which subscription operations it covers.

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?

The description gives a concrete two-step workflow: it returns how-to instructions, and then the caller executes them using the cotlet_browser_* tools in the Cloud Browser. It also explicitly says it "opens nothing by itself," which rules out expecting side effects. The only gap is the absence of a stated alternative, such as when to call the read-only get_subscription sibling instead.

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