contact_brokerSend a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| message | Yes | ||
| inquiryType | No | buying |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds the critical authentication requirement and clarifies that inquiryType selects buyer vs seller representation. It does not describe the response format or potential side effects, but the annotations cover the mutation safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is five sentences and mostly front-loaded with the core action in the first sentence. The final sentence about providing the slug and message is somewhat redundant with the schema and earlier phrasing, but the overall length is appropriate for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a small parameter set and no output schema, and the description covers the key operational aspects: auth, parameter semantics, and an alternative for finding slugs. It does not state what the response will be, but for a send-style tool this is a minor gap given the annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description compensates by explaining all three parameters: slug (broker slug, findable via search_brokers), message (the message to send), and inquiryType (buying default vs selling, with explicit semantics). This provides the agent with the meaning needed to construct a correct call.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool sends a contact message to a broker identified by their profile slug. It names the specific verb ('Send') and resource ('contact message to a broker'), which distinguishes it from sibling tools like contact_seller and search_brokers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs to use search_brokers to find broker slugs and explains how to set inquiryType for buying or selling representation. It also states the prerequisite of an authenticated account, giving the agent clear context for when to invoke the tool. However, it does not explicitly contrast with the sibling contact_seller, though the name and context make this implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: search vs. get vs. contact for brokers and businesses, list operations for categories and languages, and an auth check. There is no meaningful overlap between tools.
All tools use snake_case with a clear verb_noun structure (contact_, get_, list_, search_), and who_am_i is a conventional exception. The pattern is consistent and predictable.
Nine tools is well-scoped for a business-listing marketplace. Each tool serves a clear purpose in the discovery and contact workflow without redundancy or bloat.
The tool set covers the full user journey: searching and viewing businesses and brokers, retrieving supporting content (categories, languages), contacting parties, and verifying authentication. No critical operations are missing for the apparent domain.