Skip to main content
Glama

Get receivables report in CrewNest

crewnest_get_receivables_report
Read-onlyIdempotent

Get receivables report 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_receivables_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), the description discloses the key non-obvious behavior: the tool performs no action and returns procedural guidance that must be executed by browser tools. This is exactly the kind of context an agent cannot get from structured fields. The trailing paragraph about an unrelated Job Pricing MCP server adds no behavioral value and slightly muddies the signal.

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 two clauses are front-loaded and efficient, but the description is padded: "from ChatGPT, Claude or any AI agent" is marketing filler, and the final sentence about CrewNest's official Job Pricing MCP server is off-topic for a receivables-report tool and could mislead an agent into thinking this tool performs price calculations. Roughly a third of the text does not earn its place.

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?

There is no output schema, so the description must explain what comes back, and it does: a step-by-step walkthrough of screens, buttons, and fields, with nothing opened automatically, plus the follow-up tool family to execute it. For a zero-parameter guidance tool this covers what an agent needs to call it and act on the result; only the sibling routing is missing.

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 nothing for the description to disambiguate; the baseline applies. No parameter information is missing or contradicted.

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 states a specific verb and resource (get the receivables report) and then corrects the likely misreading by saying it returns step-by-step instructions rather than data: "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." That is a precise and unusual purpose. It loses a point because it never distinguishes itself from the sibling report tools (crewnest_get_estimate_conversion_report, crewnest_get_job_completion_report), which an agent could easily pick instead.

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: after receiving the steps, "do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser," which tells the agent how this tool fits into a sequence. However, it never says when to choose this report over the other crewnest report tools, nor any prerequisite or exclusion. Usage is implied by the topic name rather than stated.

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