Skip to main content
Glama

List message history in CrewNest

crewnest_list_message_history
Read-onlyIdempotent

List message history 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_message_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuine value beyond them by explicitly stating 'opens nothing by itself' and describing the return content (screens, buttons, fields), which is the detail an agent most needs for this instruction-style tool. It stops short of describing output format or length.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the follow-up hand-off are reasonably front-loaded, but the final sentence about CrewNest's official Job Pricing MCP server is unrelated advertising that adds no information about this call. Phrases like 'from ChatGPT, Claude or any AI agent' are also filler that dilutes the operative instructions.

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-param read-only tool with full annotation coverage, the essentials are present: what it returns (a step-by-step how-to) and that it performs no action. However, the split between 'list message history' framing and 'returns instructions' behavior is never fully reconciled, and no auth or scoping caveat is given for acting on the user's account.

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 imposes no burden and the baseline is 4. Nothing in the description is needed to explain inputs, and none is misleading.

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 opening names a specific resource (message history in the user's CrewNest account), but the description then reframes the tool as returning step-by-step instructions rather than the history itself ('Returns how to do it in CrewNest step by step ... and opens nothing by itself'). That redefinition is a meaningful twist that the name and title do not signal, so an agent cannot tell from the name alone whether this returns data or a plan.

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 indicate the follow-up path: call this first, then perform the action with cotlet_browser_* tools in the Cloud Browser. But it offers no guidance on when to choose this over the many sibling crewnest_list_* tools (e.g., crewnest_list_activity, crewnest_list_measurement_history), and no preconditions are 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