Skip to main content
Glama

Configure invoice reminders in CrewNest

crewnest_configure_invoice_reminders
Read-onlyIdempotent

Configure invoice reminders 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_configure_invoice_reminders"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the bar is lower. The description adds genuine context beyond them: the tool returns step-by-step UI instructions (screens, buttons, fields) and 'opens nothing by itself,' which clarifies it is a knowledge/guidance tool rather than an executor — a meaningful behavioral distinction.

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 sentence carries the essential meaning, but the final sentence about the official free Job Pricing MCP server is off-topic marketing text that does not help an agent select or invoke this tool. The middle sentence is also a run-on combining two ideas with a semicolon.

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?

For a zero-parameter, no-output-schema guidance tool whose annotations already cover the safety profile, the description supplies what matters: that it returns instructions and that the actual configuration happens via cotlet_browser_* tools. The only completeness lapse is the irrelevant API sentence crowding out any further useful context.

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 and schema coverage is fully reported (100%), so there is no parameter surface for the description to explain. Baseline 4 applies.

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+resource (configure invoice reminders) and explicitly reframes it as a guidance tool that 'Returns how to do it in CrewNest step by step... and opens nothing by itself.' This distinguishes it from executor-style siblings, though the trailing sentence about CrewNest's official Job Pricing API dilutes focus and adds no selection value.

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 gives a clear follow-up path: get the steps here, then 'do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser.' That is useful chaining context, but there is no explicit when-not-to-use, no prerequisites, and no differentiation from sibling config tools such as crewnest_configure_estimate_defaults or crewnest_configure_recurring_job.

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