Skip to main content
Glama

crexi_open

Open a Crexi page in your signed-in Cloud Browser to view and manage commercial real estate listings.

Instructions

Open a Crexi page in your signed-in Cloud Browser (default https://www.crexi.com) to work with commercial real estate listings.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.crexi.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the browser is 'signed-in' (auth handled) and gives the default URL, but says nothing about what happens to an already-open page (new tab vs. replace), whether a browser session must exist first, or what the call returns — there is no output schema to cover that either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the action and target first and the default URL inline. The trailing clause about commercial real estate listings adds modest domain context rather than waste.

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 one-optional-parameter navigation tool with no output schema this is nearly sufficient, but with zero annotations the missing session-prerequisite and tab-lifecycle behavior leaves an agent unable to predict side effects. It is adequate but incomplete.

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 the single optional parameter already documents its default URL. The description only restates the default, adding no syntax, format, or constraint information beyond the schema, so 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 names a specific verb and resource — 'Open a Crexi page in your signed-in Cloud Browser' — which is clearly distinguishable from crexi_click, crexi_type, and crexi_read. It does not explicitly contrast itself with those siblings, but the verb+object is unambiguous.

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?

Usage is only implied: it is the entry step before reading or clicking on listings. There is no guidance on when to call it versus crexi_status (e.g., checking for an existing session) or whether it must precede other browser tools, and no exclusions are stated.

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