Skip to main content
Glama

Tommos

Make a deal on a company

make_a_deal_on_a_company

Open a deal on a company with one of its people, as the signed-in person, as «Make a deal» on the company's page does: the deal opens through the one writer of deals on the default pipeline's first stage and names the company. contact_id is one of the company's live people (get_company's people). A company with no people makes no deal. title defaults to «New deal», currency to USD. The deal is a line of the company's history and of the audit trail.

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": {
      "company_id": "<company_id>",
      "contact_id": "<contact_id>"
    },
    "name": "make_a_deal_on_a_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
amountNo
currencyNo
company_idYesThe company's id (from list_companies)
contact_idYesThe person's contact id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, and closed-world, so the safety profile is covered. The description adds real behavioral context: the deal goes through a single writer onto the default pipeline's first stage, carries the company name, and is recorded in company history and the audit trail. It stops short of saying whether repeated calls create duplicate deals or what is returned.

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

Conciseness3/5

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

The purpose is front-loaded, but the sentence structure is a dense run-on built from colon clauses, and closing lines about the audit trail are atmospheric rather than actionable. It is informative without being wasteful, yet could be restructured for faster scanning.

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 five-parameter mutation tool with no output schema, the description covers preconditions and defaults reasonably but leaves the outcome unclear: whether a deal identifier is returned and how duplicate calls behave. Annotations cover the safety profile, so the remaining gap is moderate rather than severe.

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 only 40%, so the description must compensate; it does partially by defining contact_id as one of the company's live people and giving defaults for title (New deal) and currency (USD). The amount parameter is never mentioned, and company_id is only obliquely covered by the note that the deal names the company.

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 states a concrete verb and resource: it opens a deal on a company with one of that company's people, explicitly mirroring the «Make a deal» action on the company page. It is not tautological and conveys the scope (company-scoped deal creation), though it never contrasts itself with the other deal-creation entry points beyond the UI analogy.

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 implied through a precondition: contact_id must be a live person of the company, and a company with no people produces no deal, which effectively tells the agent when this call cannot succeed. There is no explicit when-to-use/when-not guidance relative to alternative deal-creation paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.