Skip to main content
Glama
gca-global

Qobrix CRM MCP Server

by gca-global

qobrix_list_contracts

List contracts at the Deal Signing/Close stage, linking property, contacts, and opportunity. Filter, sort, paginate, and expand related records like payment schedules and signatories.

Instructions

List contracts (RESO TransactionManagement close) — the 'Deal Signing / Payment / Close' stage of the Sales Pipeline. A Contract finalizes the transaction: it links the Property, buyer/seller Contacts, and the Opportunity. Returns { data: [...], pagination: { count, current_page, has_next_page, ... } }. Verified include: Contacts, PropertyIdProperties, OpportunityIdOpportunities, PaymentInstallments (payment schedule), ContractParties (all signatories), CreatedByUsers. Canonical chain: Offer → Contract → Payment → Close. After contract signing, the property status moves to 'reserved' (Pending), then 'sold' (Closed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1). Used on the fast path (no boost). Ignored when boost is set (ranking returns a single top-N page).
sortNoSort by field name (maps to Qobrix OpenAPI sort[]). Prefix with - for descending. Comma-separated for multi-key (e.g. '-list_selling_price_amount,-created'). Examples: '-created' (newest first), 'name' (alphabetical), '-list_selling_price_amount' (highest list price first).
limitNoHow many results to return (1-100, default 10). With boost: top-N after ranking. Without boost: page size. Raise when the user wants more options; keep low to avoid context overload.
searchNoHard-filter Qobrix search expression (server-side precision). Operators: == != <> < > <= >=, contains, starts with, ends with, in [...], not in, ranges in a..b, and/or/not. Functions: DISTANCE_FROM, IN_POLYGON, TRANSLATED, MIN/MAX, DAYS_AGO(n), MONTHS_AGO(n), DAYS_FROM_NOW(n). Shortcuts: NOW, TODAY, THIS_WEEK, LAST_MONTH, THIS_YEAR, CURRENT_USER. Strings double-quoted; booleans true/false; association paths e.g. SalespersonUsers.Contacts.country. Example: status == "available" and sale_rent == "for_sale" and list_selling_price_amount <= 500000. For the full grammar + field cheatsheets call qobrix_search_dsl_help. For enum values call qobrix_get_field_options; for all fields call qobrix_get_schema.
includeNoAssociations to expand. Verified options: Contacts, PaymentInstallments, ContractParties, PropertyIdProperties, OpportunityIdOpportunities, CreatedByUsers
Behavior4/5

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

No annotations are present, but the description provides valuable behavioral context: it discloses the return shape ({ data, pagination }), lists verified includes, and explains the downstream effect on property status ('reserved' then 'sold'). It does not explicitly state read-only behavior, but the listing nature implies it.

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?

The description is moderately long but front-loaded with the core action. Every section (stage, return shape, includes, canonical chain, status change) contributes value, though it could be slightly more concise. No fluff.

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 no output schema, the description compensates by providing the return shape and pagination keys. It also adds rich domain context (pipeline stage, relationships, property status flow) that helps the agent understand the tool's role among many sibling tools. Minor gap: no explicit alternative tool guidance.

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 description coverage is 100%, so the schema already documents all 5 parameters. The tool description adds no new parameter-specific semantics; it merely repeats the verified include options that are already in the schema's include description. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'List contracts' and specifies the business stage (RESO TransactionManagement close, Deal Signing/Payment/Close). It defines what a contract is and its relationships, distinguishing it from other list/get/search tools by contextualizing it within the sales pipeline.

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?

The description implies usage when dealing with contracts in the sales pipeline and mentions the canonical chain (Offer → Contract → Payment → Close), but it does not explicitly state when to use this list tool versus qobrix_search_contracts or qobrix_get_contract. No alternatives or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gca-global/qobrix-crm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server