Skip to main content
Glama
Sign In
rd-station-crm

rd-station-crm

by juliano09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rdstation_win_deal

Update a deal's status to won in RD Station CRM, ensuring accurate pipeline tracking.

Instructions

Mark a deal as won in RD Station CRM.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "rdstation_win_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral details. It reveals the mutation ('mark as won') but not side effects, reversibility, required permissions, or what happens to a deal already won or lost. This is a significant gap for a state-changing tool.

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?

One clear sentence with no filler. The action, resource, and system are stated compactly and the sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation with no annotations and no output schema, the definition is incomplete: it doesn't describe return values, side effects like setting a close date, or expected behavior on already-won/lost deals. An agent can make the call but cannot predict the outcome.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not compensate: it never explains deal_id's format or that it is the RD Station deal identifier beyond what the name implies. The single parameter is self-evident in context, but the definition adds no real semantic value.

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 clear action ('Mark a deal as won') and a specific resource (deal in RD Station CRM), so an agent can distinguish it from siblings like rdstation_lose_deal. It lacks an explicit mention of the alternative operation, but the verb and target state are unambiguous.

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 intended use is implied: call this when a deal reaches a won state. However, the description gives no explicit guidance about when not to use it or when to prefer update_deal/lose_deal, so usage guidance is only implicit.

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

Deploy Server

Other Tools