Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Post a deal to Deals

connections_deal_create
Destructive

Use this when the member asks to post a deal, list a raise, sell a business or asset, or look for a partner, buyer or investment on Deals. Creates one deal. publish true (the default) makes it live immediately when title and full_description are both present; false saves a draft to finish later. A public listing is seen by everyone on the marketplace. Posting a LIVE listing needs a paid plan: on an account without one the reply says so instead of creating anything, and a draft can still be saved on any plan. Set dry_run true to see the exact call and outcome without creating anything.

Input Schema

NameRequiredDescriptionDefault
titleYesOne line naming the deal.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
regionNoCity or region. Optional, and it is what makes a listing findable by region.
dry_runNotrue previews the exact call and its outcome without creating or changing anything.
projectNoWorkspace to run this call in (id or name).
publishNotrue (default) makes the deal live now if every required field is present. false saves it as a draft.
summaryNoOne or two sentences, shown on the marketplace feed.
categoryNoe.g. 'real-estate', 'saas', 'services'. Optional, and it is what makes a listing findable by category.
passwordNoRequired when visibility is 'private' - the access password for the deal's page.
visibilityNopublic (default) is listed on the marketplace. private needs `password` too and is reachable only by direct link.
deal_intentNoWhether the member is selling/raising ('selling') or looking for capital, a partner or a buyer ('looking').
capital_soughtNoOptional amount being raised or asked.
min_investmentNoOptional minimum investment or ticket size.
expected_returnsNoOptional, free text.
full_descriptionNoThe full pitch/details. Required to publish - with title, it is the whole publish requirement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"e.g. 'real-estate', 'saas', 'services'. Required to publish."New value: +"e.g. 'real-estate', 'saas', 'services'. Optional, and it is what makes a listing findable by category."
    • changedInput schema / properties / full_description / description
      Previous value: -"The full pitch/details. Required to publish."New value: +"The full pitch/details. Required to publish - with title, it is the whole publish requirement."
    • changedInput schema / properties / region / description
      Previous value: -"City or region. Required to publish."New value: +"City or region. Optional, and it is what makes a listing findable by region."
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it warns that a live listing is visible to everyone on the marketplace, that publishing requires a paid plan (with the failure mode explained rather than just failing), that drafts work on any plan, and that dry_run previews the exact call. These are exactly the consequences an agent needs before making a destructive, non-idempotent, open-world call.

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

Conciseness5/5

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

Five short sentences, front-loaded with the trigger condition, then creation semantics, then plan gating, then the dry_run escape hatch. No filler and nothing repeated from the schema verbatim.

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 15-parameter mutation tool with no output schema, the description covers the high-stakes behaviors (live vs draft, paid plan, public exposure, dry run). It leaves the workspace/person scoping parameters and private-visibility flow unexplained, though those are self-documented in the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining cross-parameter behavior the schema cannot: publish=true only goes live when title AND full_description are both present, and the plan gate applies only to live listings. It does not touch visibility/password pairing, but the schema already covers that.

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+resource ("Creates one deal") and enumerates the user intents that trigger it (post a deal, list a raise, sell a business, find a buyer/partner). This clearly separates it from the read-side siblings connections_deals_list and connections_deals_search.

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?

Opens with an explicit "Use this when the member asks to..." trigger list and clarifies the publish-vs-draft decision point. It does not name the sibling tools (deals_list, deals_search) as alternatives, so an agent must still infer that reading deals is a different call.

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

All Connections 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