Tendeck: AI-run real estate CRM + broker recruiting

support_status

Check a support ticket you filed earlier and read the Tendeck team's reply or fix. Call it with the ticket and the status_token that support_report returned; when you are signed in to the same workspace you can pass the ticket alone. Tell the user plainly what the reply says and whether they need to do anything.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticket": "<ticket>"
    },
    "name": "support_status"
  }
}

Input Schema

Name	Required	Description	Default
`ticket`	Yes	The ticket code, like SUP-7KQ4M2.
`status_token`	No	The status_token support_report returned (not needed when signed in).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose the real behavioral trait that matters: authentication state changes the required inputs. It still omits what happens on an invalid/expired ticket or status_token, and whether lookups are rate-limited or scoped by workspace membership beyond the auth hint.

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?

Three sentences, front-loaded with the purpose, then the invocation rule, then the presentation instruction. Each contributes, though the final user-facing phrasing sentence is guidance rather than tool semantics and could be trimmed.

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?

No output schema exists, and the description does sketch the return ('the reply or fix') and how to relay it, plus the conditional-auth input rule. Missing only edge-case behavior (invalid token, ticket not found), so it is nearly complete for a 2-parameter read tool.

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 schema already explains both fields, including that status_token is not needed when signed in. The description restates that same provenance detail rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Check a support ticket... and read the Tendeck team's reply or fix') and scopes it to tickets the caller filed earlier, which cleanly separates it from the filing-oriented sibling support_report. An agent can pick it without opening the schema.

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?

Gives clear invocation context: pass ticket plus the status_token support_report returned, or ticket alone when signed in to the same workspace. That implicitly routes ticket creation to support_report but never explicitly says when not to use this tool or what to do if the lookup fails.

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

All Tendeck: AI-run real estate CRM + broker recruiting 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?