Cria um evento de conversão na RD Station Marketing (POST /platform/events). Passe 'event' com o payload completo (event_type, event_family, payload com email, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
| event | Yes | ||
| account | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. Description adds that it creates an event and hints at payload structure (event_type, event_family, email). However, no details on idempotency, rate limits, or side effects beyond creation.
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?
Two sentences, no fluff. First sentence states purpose clearly, second gives parameter guidance. Perfectly concise and front-loaded.
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?
Minimally adequate: explains creation and payload hint, but missing explanation for optional 'account' parameter, no return value info, no error handling. Given complexity (nested object), more detail would help.
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?
Schema has 0% description coverage; the description provides necessary guidance on the 'event' parameter's structure (event_type, event_family, payload with email), compensating for the schema's lack of detail. However, the 'account' parameter remains unexplained.
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?
Description explicitly states it creates a conversion event in RD Station Marketing, specifying the HTTP method and endpoint. This clearly distinguishes it from sibling tools dealing with contacts, webhooks, accounts, etc.
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?
No guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or when not to use. The description only says to pass the event payload.
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.