Skip to main content
Glama

Get job completion report in CrewNest

crewnest_get_job_completion_report
Read-onlyIdempotent

Get job completion 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_job_completion_report"
  }
}

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, idempotentHint and destructiveHint=false, but the description adds a genuinely useful disclosure beyond them: it 'opens nothing by itself' and only returns instructions, so the agent knows no state changes occur in CrewNest. It also scopes the data to the user's own account. It stops short of describing the returned step format or coverage limits.

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 is front-loaded and actionable in sentence two, but the third sentence about CrewNest's official free Job Pricing MCP server is promotional filler unrelated to completing a job completion report and dilutes the definition. The embedded 'then do it with the cotlet_browser_* tools' clause is dense but earns its place.

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 setting expectations, and it leaves unclear what the report covers and what the returned step-by-step content looks like. For a guided-workflow tool it is adequate to call correctly, but an agent cannot predict the response shape or whether the report is scoped to a time period.

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 and the baseline is 4. The description does not explain that no date range or job filter can be supplied, which is a minor missed opportunity given agents often expect report filters.

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 first sentence names a specific verb and resource (get job completion report), but the second sentence reveals the tool actually returns step-by-step instructions rather than the report itself, which blurs what the agent will receive. It never says what the report contains (completion rates, job counts, time window), and does not distinguish it from sibling report tools like crewnest_get_estimate_conversion_report or crewnest_get_receivables_report.

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?

There is a clear workflow handoff: use this to learn the steps, then act with the cotlet_browser_* tools in the CrewNest Cloud Browser. However, there is no guidance on when to pick this report versus the other crewnest_get_*_report siblings, and the trailing note about a separate official Job Pricing MCP server is unrelated to report selection and adds no actionable routing.

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