Ragently CRM

Deal naar andere fase

crm_verplaats_deal

Idempotent

Verplaats een deal naar een andere fase (een gesloten fase van het soort gewonnen of verloren sluit de deal). Zelfde fase: geen wijziging.

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>",
      "fase": "<fase>"
    },
    "name": "crm_verplaats_deal"
  }
}

Input Schema

Name	Required	Description
`fase`	Yes	Fasenaam uit de pijplijn van dit account; een onbekende naam geeft een fout met de bekende fases.
`agent`	No	Optioneel: naam van de agent of het script dat dit doet; wordt als 'door' vastgelegd.
`deal_id`	Yes	Deal-id

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description's added value is the side effect: a closed won/lost phase actually closes the deal, which is not derivable from the annotations or schema. It also confirms the no-op case for an unchanged phase. It does not mention permissions, audit/notification side effects, or what the response contains.

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?

Two short sentences, front-loaded with the action and immediately followed by the closing side effect and the no-op case. No redundant restatement of the title or name.

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 three-parameter mutation tool with full schema coverage and rich annotations, the description covers the key non-obvious behavior (deal closing) and the idempotent no-op. Remaining gaps — whether closing triggers automation/notifications and required permissions — are modest but real for a state-changing 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 description coverage is 100%, so the schema already explains fase (must be a pipeline phase name, unknown names error out), deal_id, and agent. The description adds nothing parameter-specific, so the baseline 3 applies.

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?

"Verplaats een deal naar een andere fase" states a specific verb and resource, and the parenthetical adds the important consequence that a closed won/lost phase closes the deal. It does not explicitly name the sibling it differs from (e.g. crm_bewaar_deal, which can also set a phase), so differentiation is inferable rather than stated.

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 by the verb: call this when a deal must change phase. There is no explicit when-to-use versus crm_bewaar_deal, no preconditions (e.g. deal must exist, pipeline must belong to the account), and no when-not guidance. The "same phase: no change" note is behavioral rather than routing guidance.

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

All Ragently CRM 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?