Skip to main content
Glama

Measure property in CrewNest

crewnest_measure_property
Read-onlyIdempotent

Measure property 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_measure_property"
  }
}

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 safety profile is covered. Beyond that, the description usefully discloses the shape of the output (step-by-step screens/buttons/fields) and explicitly states the tool performs no action or opening on its own, which is exactly the context an agent needs to avoid treating the call as an executor. It does not say whether a Cloud Browser session must already exist before calling.

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 sentences are well ordered: what you get, what it does not do, and how to act on it. The final sentence about CrewNest's official Job Pricing MCP server is a non-sequitur for a measure-property tool and does not earn its place. The opening sentence also spends words on 'from ChatGPT, Claude or any AI agent,' which adds no decision-relevant information.

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 guidance tool with no output schema, the description covers the essentials: it explains that the return value is procedural instructions and that a separate browser tool must carry out the work. What is missing is any mention of preconditions (an active Cloud Browser session, being signed in) or what the guidance does not cover, but the definition is otherwise sufficient to call correctly.

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 the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; the description is consistent with a no-argument tool.

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 makes the key distinction that this tool returns step-by-step how-to guidance (screens, buttons, fields) rather than performing the measurement, and explicitly says it 'opens nothing by itself.' That separates it from the cotlet_browser_* executors. The opening clause 'Measure property in the user's own CrewNest account' largely restates the title and never defines what 'measure' means in CrewNest, so the verb/resource statement is softer than it could be.

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 execute them with cotlet_browser_* in the Cloud Browser. There is no explicit when-not guidance and no named sibling alternatives within the crewnest_* family. The closing remark about an official Job Pricing MCP server hints at an alternative for price calculations but names no tools and states no selection condition, so it adds ambiguity more than routing.

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