Skip to main content
Glama

Read customer portal in CrewNest

crewnest_read_customer_portal
Read-onlyIdempotent

Read customer portal 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_read_customer_portal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the non-obvious fact that the tool 'opens nothing by itself' and returns procedural guidance rather than portal data. That is meaningful disclosure beyond the structured fields. It stops short of noting prerequisites (whether the user must be signed in or have a portal already configured).

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 core, useful content is one sentence. The opening clause duplicates the tool name, and the trailing sentence about CrewNest's 'official, free Job Pricing MCP server with three read-only tools' is unrelated promotional material that does not help an agent decide to call this tool.

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, annotation-covered, no-output-schema tool, the description supplies the essential missing pieces: what is returned (step-by-step instructions) and what to do next (browser tools). Additional detail on failure or prerequisite conditions would be nice but is not critical here.

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 no parameter semantics to explain and the baseline of 4 applies. The description does not introduce any confusion about inputs.

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 second sentence gives a concrete statement of what the tool actually produces: step-by-step CrewNest instructions (screens, buttons, fields) with no side effects, and it names the cotlet_browser_* tools as the acting counterpart. The opening sentence is largely a restatement of the name and slightly oversells it as 'Read customer portal', but the real behavior is still recoverable.

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 establishes an explicit two-stage workflow: use this tool to learn the procedure, then execute it with cotlet_browser_* in the Cloud Browser. It does not, however, distinguish this from crewnest_generate_customer_portal_link or say when a user would want a portal link instead of guided steps, so the sibling routing is only partially covered.

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