Skip to main content
Glama

List document approvals in CrewNest

crewnest_list_document_approvals
Read-onlyIdempotent

List 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_list_document_approvals"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered. Beyond that, the description usefully discloses that the tool "opens nothing by itself" and returns a step-by-step walkthrough (screens, buttons, fields), which tells the agent the return value is procedural guidance rather than approval records — a genuinely additive behavioral fact.

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 first two sentences are dense and front-load the actual behavior plus the handoff to browser tools. The closing sentence about CrewNest's unrelated Job Pricing MCP server earns no place here — it describes a different server entirely and distracts from how to call this tool.

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, read-only tool with no output schema, the description covers the essential contract: no data is fetched, instructions are returned, and browser tools do the actual work. What's missing is the shape of that returned guidance and any differentiation from the sibling review tool, leaving the agent to guess at the boundary.

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 requires no elaboration and the baseline is 4. The description correctly adds no parameter discussion, though it also doesn't clarify whether the listing is scoped or filtered in any implicit way.

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 specific resource (document approvals) and account scope (the user's own CrewNest account), but the headline verb "List" is undercut by the body, which says it "Returns how to do it in CrewNest step by step" and "opens nothing by itself." An agent is left to reconcile whether this returns approval data or navigation instructions, and the sibling crewnest_review_document_approvals is never mentioned.

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?

Usage is implied rather than stated: the description directs the agent to use cotlet_browser_* tools afterward, which signals this is a preparatory/guidance step. However, it never says when to choose this over the similarly named review_document_approvals tool, and no exclusions or preconditions are given.

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