Skip to main content
Glama

Review team request in CrewNest

crewnest_review_team_request
Read-onlyIdempotent

Review team request 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_review_team_request"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description adds the genuinely important behavioral fact that the tool "opens nothing by itself" and instead returns instructional content, plus the external dependency on the cotlet_browser_* tool family. That goes meaningfully beyond the annotations. The trailing sentence about a Job Pricing MCP server adds no behavioral information about this tool.

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 purpose and the follow-up mechanism are front-loaded and efficient. The final sentence about CrewNest's free Job Pricing MCP server with three read-only tools is unrelated promotional content that does not help an agent decide or invoke this tool, and it dilutes the definition.

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?

The description covers what the tool returns (step-by-step screens/buttons/fields) and that it does not act, which is the essential information given no output schema. It leaves unanswered how an agent knows which team request is being reviewed when there are no parameters, and whether the result enumerates pending requests or assumes a specific one.

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 schema baseline of 4 applies and there are no parameter semantics the description is obliged to explain. It could still have clarified how the target team request is identified given the absence of any identifier argument, but that is a scope question rather than a parameter-documentation gap.

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 a specific verb and resource ("Review team request in the user's own CrewNest account") and clarifies the crucial twist that it returns step-by-step instructions on screens, buttons and fields rather than performing the review. It does not differentiate itself from the near-identical sibling crewnest_review_booking_request or crewnest_review_document_approvals, so an agent must infer the distinction from the request type alone.

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?

Implied usage is clear (call this to learn how to review a team request), and it gives a useful follow-up instruction to act via the cotlet_browser_* tools in the Cloud Browser. However, it never states when to prefer this over the booking/document review siblings, nor any preconditions or exclusions.

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