Skip to main content
Glama

Manage message template in CrewNest

crewnest_manage_message_template
Read-onlyIdempotent

Manage message template 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_manage_message_template"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it explicitly says it 'opens nothing by itself' and that the actual change happens via cotlet_browser_* tools, which prevents an agent from mistaking it for a mutation or assuming the operation completed after calling it.

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 clear, but the closing sentence about CrewNest publishing a free Job Pricing MCP server with read-only pricing tools is promotional and irrelevant to invoking this tool — it burns attention without adding operational value.

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, read-only instructional tool with no output schema, the definition covers what it returns (screens, buttons, fields) and what must follow (cotlet_browser_* execution), which is what an agent needs. The remaining gap is scope: it never enumerates what aspects of a message template are covered or what state the account must be in.

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 no parameter semantics burden on the description and the baseline of 4 applies. The schema is empty with additionalProperties=false, matching the description's implication that no inputs are needed.

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 resource is specific (message template in the user's CrewNest account) and the description usefully clarifies that the tool returns step-by-step instructions rather than performing the action. However, the verb 'manage' is vague — it doesn't say whether this covers creating, editing, deleting, or viewing templates — and nothing distinguishes it from siblings such as crewnest_list_message_history.

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 statement: call this to get the steps, then execute them with cotlet_browser_* tools in the Cloud Browser. That is genuine when-to-use guidance, but there are no exclusions, no statement of when a direct API/action tool would be preferable, and no prerequisites or preconditions described.

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