Skip to main content
Glama

List calendar in CrewNest

crewnest_list_calendar
Read-onlyIdempotent

List calendar 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_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description adds the non-obvious behavioral fact that the call mutates nothing and merely returns procedural instructions, with the real action delegated to cotlet_browser_* tools. That is meaningful disclosure an agent could not infer from the annotations alone, though the closing sentence about an unrelated Job Pricing MCP server adds confusion 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 actionable content (what it returns, and that a browser tool does the real work) is front-loaded, but the second sentence is a dense run-on and the third sentence is pure promotional padding about CrewNest's official API and Job Pricing MCP server that does not help an agent select or invoke this tool.

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-parameter, no-output-schema tool the description does cover what comes back (screens, buttons, fields), but it leaves the central ambiguity unresolved: whether any calendar data is ever returned, or only instructions. The trailing tangent about a separate MCP server further muddies rather than completes the picture.

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 to explain and the baseline of 4 applies. The schema closes with additionalProperties=false, and nothing in the description misstates the calling contract.

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 first sentence names a specific verb and resource ('List calendar in the user's own CrewNest account') and, unusually, discloses that the tool returns step-by-step guidance rather than the calendar data itself. That disclosure is valuable, but it undercuts the plain reading of the name, and the description never differentiates this list tool from the many sibling list_* tools (crewnest_list_jobs, crewnest_list_activity, etc.).

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 one concrete routing instruction: use the cotlet_browser_* tools in the CrewNest Cloud Browser to actually perform the listing. It does not say when to choose this tool over sibling list_* tools, nor what preconditions (an active Cloud Browser session, logged-in account) are required before the follow-up browser call will succeed.

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