Mashvisor MCP Server and API by Cotlet

Get property analysis in Mashvisor

mashvisor_get_property_analysis

Read-onlyIdempotent

Get property analysis in the user's own Mashvisor account from ChatGPT, Claude or any AI agent. Returns how to do it in Mashvisor step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Mashvisor Cloud Browser. Mashvisor's official API: Mashvisor has a REST Data API, sold as a separate product with an API key: a free tier of 30 one-time sample requests, then plans from $129 a month for 500 calls (checked 11 Oct 2026).

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": "mashvisor_get_property_analysis"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the key behavioral fact that it 'opens nothing by itself' — i.e. it returns instructions only and performs no UI action. It also explains via the official-API note why a UI-guide tool is needed, which is useful context beyond the annotations.

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 behavior is stated early, but the opening clause about 'ChatGPT, Claude or any AI agent' is filler and the API pricing paragraph (free tier, $129/month, checked date) is tangential detail that dilutes focus. The essential information could be delivered in about half the length.

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?

With zero parameters and no output schema, the description carries the burden of explaining what comes back, and it does: a step-by-step guide with screens, buttons and fields. It also names the sibling tools needed to act on that guide, leaving only minor gaps around prerequisites for the user's Mashvisor account or plan.

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 per the baseline this scores 4. There is nothing for the description to disambiguate, and it correctly signals that no input is needed to obtain the guide.

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 corrects the potentially misleading name by stating explicitly that the tool 'Returns how to do it in Mashvisor step by step (screens, buttons, fields)' rather than returning analysis data, and it names the follow-up tool family (cotlet_browser_*). It could do more to distinguish itself from cotlet_app_guide, which appears to serve a similar guidance role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage sequence: call this first to get the step-by-step, then execute with cotlet_browser_* tools in the Mashvisor Cloud Browser. It does not state when to prefer this over cotlet_app_guide or mashvisor_run_saved_search, so the alternative-selection guidance is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mashvisor MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?