Skip to main content
Glama

Get subscription in CrewNest

crewnest_get_subscription
Read-onlyIdempotent

Get 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_get_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds a genuinely non-obvious behavioral fact: the tool "opens nothing by itself" and only returns procedural steps. That prevents an agent from assuming the call performed the action. It could go further and say whether the guide is account-specific or static.

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 two core sentences earn their place, but the closing sentence about CrewNest's official Job Pricing MCP server is unrelated advertising that does not help the agent call this tool and dilutes an otherwise short definition. The middle clause about the browser tools is also buried rather than front-loaded.

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?

With annotations covering safety, no output schema, and zero params, the description is nearly complete — it explains the return shape (screens, buttons, fields) and the follow-up step. The missing piece is the relationship to `crewnest_manage_subscription`: an agent cannot tell from this text whether the mutation sibling exists or when to prefer it.

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. There is nothing for the description to disambiguate, and it correctly implies no input is required.

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 does eventually state the real output: it "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." But the opening verb phrase "Get subscription in the user's own CrewNest account" and the title both imply data retrieval, which contradicts the guide/instruction nature of the tool. It also never distinguishes itself from the nearby `crewnest_manage_subscription` sibling, leaving the agent to guess which one to pick.

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 useful forward guidance: after calling this, perform the action with the `cotlet_browser_*` tools in the user's CrewNest Cloud Browser, which establishes the two-step workflow. However, there is no statement of when to use this instead of `crewnest_manage_subscription`, and no preconditions such as whether the user must be signed in or have an active account.

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