Skip to main content
Glama
Sign In

Crexi MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: how to work in an app

cotlet_app_guide
Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Crexi it covers these actions: Export leads, List saved searches, Get comps, Get listing analytics, Create listing.

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

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Crexi.
taskNoWhat the user wants done in the app, in their words.

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?

Adds real behavior beyond the annotations: it is free, opens no browser session, and works for apps outside Cotlet's catalog via a general method. The readOnly/openWorld/idempotent hints are consistent with this. The main thing left unspecified is what the returned guide actually looks like (no output schema), which keeps it below 5.

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 core instruction is front-loaded, but it is a single run-on sentence of enumerations piled onto enumerations ("the app's screens, menus and actions, notes, and the app's dedicated tools..."), followed by a dangling list of Crexi actions appended to the final sentence. Splitting into the what / when / scope structure would make it far easier to parse.

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 two-optional-param, free, read-only guide tool, the definition covers usage timing, scope, catalog fallback, and concrete coverage examples. With no output schema, it could say more about the shape of the returned guide, but an agent has enough to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both params are documented in the schema (app name/slug with Crexi default, task in user's words). The description adds the useful nuance that non-catalog apps fall back to a general method and enumerates the covered Crexi actions, but it doesn't explain how 'task' shapes the guide's output. Baseline 3 applies.

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 states a specific purpose: a pre-flight guide for driving a web app in the user's Cloud Browser with Cotlet's browser tools, covering which browser/sign-in link, the step-by-step method, screens/menus/actions, notes, and app-specific tools. It is distinguishable from the browser_* siblings (which perform actions) and from cotlet_apps (catalog), though it never names a sibling directly.

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?

"Call it before the first browser step in an app" gives explicit timing, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets the boundary. It also lists the concrete Crexi actions covered. It stops short of naming explicit alternatives or when-not-to-use, so it is clear context rather than full routing guidance.

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

All Crexi MCP Server and API by Cotlet toolsInspect
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