Skip to main content
Glama

List measurement history in CrewNest

crewnest_list_measurement_history
Read-onlyIdempotent

List measurement 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_measurement_history"
  }
}

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, idempotentHint, and destructiveHint=false, so safety is partly covered, but the description adds the crucial non-obvious fact that the tool 'opens nothing by itself' and instead returns procedural instructions. That prevents an agent from assuming a real data fetch occurred — a real behavioral disclosure. The closing sentence about CrewNest's official Job Pricing MCP server is unrelated to invoking this tool and reads as promotion rather than behavior.

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 operative content is front-loaded and useful, but it is buried in long compound sentences with an awkward parenthetical. The final sentence about the official Job Pricing MCP server does not help an agent call this tool and should be cut.

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, non-destructive tool with no output schema, the description covers what matters most: it returns step-by-step instructions rather than data, takes no action itself, and should be followed by cotlet_browser_* calls. It could go further on what form the instructions arrive in, but nothing essential is missing for correct invocation.

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. Baseline for a no-parameter schema applies.

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 description says it will 'List measurement history in the user's own CrewNest account' and then clarifies that it actually 'Returns how to do it in CrewNest step by step (screens, buttons, fields)' rather than the data itself. That clarification is valuable, but it conflicts with the tool name/title, so an agent skimming only the name may expect measurement records back. The description also never distinguishes this from sibling list tools such as crewnest_list_message_history or crewnest_list_activity.

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 concrete next-step guidance: after reading the instructions, 'do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser.' That tells the agent this is a preparatory call, which is genuinely useful. However, there is no statement of when to prefer this tool over a sibling list tool, and no precondition or exclusion is given.

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