Skip to main content
Glama

Review document approvals in CrewNest

crewnest_review_document_approvals
Read-onlyIdempotent

Review document approvals 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_document_approvals"
  }
}

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 readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds genuinely useful behavior beyond them by stating it "opens nothing by itself" and returns screens/buttons/fields instructions instead of taking action. The final sentence about CrewNest's separate Job Pricing MCP server adds noise rather than behavioral insight.

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 key operational fact — that it returns instructions and performs nothing — is buried in the second sentence rather than front-loaded. The third sentence about CrewNest's free Job Pricing MCP server with three read-only tools is irrelevant padding that does not help an agent decide or act.

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 no parameters and no output schema, the description carries the burden of explaining what comes back, and it does say the return is step-by-step screens/buttons/fields. That is adequate but not complete: it omits any hint of the guidance's length or structure and leaves the relationship to crewnest_list_document_approvals unresolved, which is the main ambiguity for an agent at selection time.

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 (empty object schema, 100% coverage), so there is nothing for the description to disambiguate; a 4 is the appropriate baseline. The description correctly implies no inputs are needed to obtain the guidance.

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 description names a specific verb and resource ("Review document approvals in ... CrewNest") and clarifies in the second sentence that the tool actually returns step-by-step instructions rather than performing the review. It never distinguishes itself from the near-identical sibling crewnest_list_document_approvals, so an agent must guess which one returns data versus guidance.

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?

It does give a forward workflow ("then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser"), which tells the agent what to do after calling. However, it never states when to choose this tool over the obvious alternative crewnest_list_document_approvals, and offers no exclusions or prerequisites for the "user's own account" scoping.

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