Comunicate.top

Comandă redactarea unui articol (cheltuiește)

order_writing

Destructive

Cere echipei platformei să scrie articolul: temă, tip de campanie, lungime, cuvânt-cheie, brand, adresa promovată, fapte. Se plătește din sold. Merge doar cu comutatorul pentru asistenți AI pornit.

Use when the user explicitly asks the platform team to write an article and accepts the cost. Spends money. Do not use when the user brings their own text: use create_article.

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": {
      "tema": "<tema>"
    },
    "name": "order_writing"
  }
}

Input Schema

Name	Required	Description
`note`	No	Alte indicații pentru redactor (ton, ce să evite).
`tema`	Yes	Despre ce e articolul. Ex.: Deschiderea unei clinici stomatologice în Cluj
`brand`	No	Brandul sau firma despre care se scrie.
`fapte`	No	Faptele care trebuie să apară (cifre, date, citate), câte unul pe element.
`cuvinte`	No	Lungimea articolului, în cuvinte.
`campaignId`	No	Campania în care intră articolul livrat, din list_campaigns.
`cuvantCheie`	No	Cuvântul-cheie pe care îl susține articolul (la SEO). Ex.: implant dentar Cluj
`campaignType`	No	Tipul articolului de scris: SEO, BRAND_AWARENESS, PRESS_RELEASE, BRAND_MENTION, CASINO, CRYPTO sau ADULT.
`idempotencyKey`	No	O cheie unică aleasă de tine: o comandă repetată cu aceeași cheie nu se plătește de două ori.
`adresaPromovata`	No	Pagina spre care trimite linkul din articol, adresă https.

Output Schema

Name	Required	Description
`id`	No	string. The writing order.
`status`	No	string
`articleId`	No	string\|null. The delivered article, once ready.
`priceCents`	No	number. Price in bani, VAT excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 7, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / campaignId / description

Previous value: -"Campania în care intră articolul livrat (UUID), din list_campaigns."New value: +"Campania în care intră articolul livrat, din list_campaigns."

removedInput schema / properties / campaignId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedInput schema / properties / cuvinte / description

Previous value: -"Lungimea articolului, în cuvinte: 500, 700, 1000 sau 1500."New value: +"Lungimea articolului, în cuvinte."

changedInput schema / properties / fapte / description

Previous value: -"Faptele care trebuie să apară (cifre, date, citate), câte unul pe element, cel mult 20."New value: +"Faptele care trebuie să apară (cifre, date, citate), câte unul pe element."

changedInput schema / properties / note / description

Previous value: -"Alte indicații pentru redactor (ton, ce să evite), cel mult 2.000 de caractere."New value: +"Alte indicații pentru redactor (ton, ce să evite)."

changedInput schema / properties / tema / description

Previous value: -"Despre ce e articolul, 10–200 de caractere. Ex.: Deschiderea unei clinici stomatologice în Cluj"New value: +"Despre ce e articolul. Ex.: Deschiderea unei clinici stomatologice în Cluj"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "articleId": {
+      "description": "string|null. The delivered article, once ready."
+    },
+    "id": {
+      "description": "string. The writing order."
+    },
+    "priceCents": {
+      "description": "number. Price in bani, VAT excluded."
+    },
+    "status": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

Changed10 schema fields changedNov 7, 2026

addedInput schema / properties / adresaPromovata / description

Added value: +"Pagina spre care trimite linkul din articol, adresă https."

addedInput schema / properties / brand / description

Added value: +"Brandul sau firma despre care se scrie."

addedInput schema / properties / campaignId / description

Added value: +"Campania în care intră articolul livrat (UUID), din list_campaigns."

addedInput schema / properties / campaignType / description

Added value: +"Tipul articolului de scris: SEO, BRAND_AWARENESS, PRESS_RELEASE, BRAND_MENTION, CASINO, CRYPTO sau ADULT."

addedInput schema / properties / cuvantCheie / description

Added value: +"Cuvântul-cheie pe care îl susține articolul (la SEO). Ex.: implant dentar Cluj"

addedInput schema / properties / cuvinte / description

Added value: +"Lungimea articolului, în cuvinte: 500, 700, 1000 sau 1500."

addedInput schema / properties / fapte / description

Added value: +"Faptele care trebuie să apară (cifre, date, citate), câte unul pe element, cel mult 20."

addedInput schema / properties / idempotencyKey / description

Added value: +"O cheie unică aleasă de tine: o comandă repetată cu aceeași cheie nu se plătește de două ori."

addedInput schema / properties / note / description

Added value: +"Alte indicații pentru redactor (ton, ce să evite), cel mult 2.000 de caractere."

addedInput schema / properties / tema / description

Added value: +"Despre ce e articolul, 10–200 de caractere. Ex.: Deschiderea unei clinici stomatologice în Cluj"

Changed5 schema fields changedNov 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / campaignId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / cuvinte / anyOf

Added value: +[
+  {
+    "const": 500,
+    "type": "number"
+  },
+  {
+    "const": 700,
+    "type": "number"
+  },
+  {
+    "const": 1000,
+    "type": "number"
+  },
+  {
+    "const": 1500,
+    "type": "number"
+  }
+]

removedInput schema / properties / cuvinte / enum

Removed value: -[
-  500,
-  700,
-  1000,
-  1500
-]

removedInput schema / properties / cuvinte / type
```
Removed value: -"number"
```

First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the crucial business consequence: the order is charged against the account balance, and it only works when the AI-assistant switch is enabled. It still does not explain what happens on failure or whether a charge is refunded, which matters for a paid mutation, hence 4 rather than 5.

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

Conciseness4/5

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

Front-loaded with the core action and the cost/prerequisite warnings come before usage guidance, which is the right order for a spending tool. There is mild redundancy: the title already says '(cheltuiește)' and the body repeats 'Se plătește din sold' and 'Spends money' twice, and the language mixes Romanian and English.

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 10-parameter paid mutation with an output schema, the description covers the decisive facts an agent needs: cost, prerequisite switch, and the alternative for owned text. Remaining gaps (failure/refund behavior, which fields are mandatory) are either minor or already handled by the schema.

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 every parameter including the idempotency key and the fixed word-count enum is already documented in the schema. The description's parameter list merely restates field names already present in structured data, adding no syntax, format or constraint detail beyond it. Baseline 3 applies.

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?

The description states a specific verb and resource: it asks the platform team to write an article, and it enumerates the inputs that shape the output (topic, campaign type, length, keyword, brand, promoted address, facts). It also names the sibling it is not (create_article) for user-supplied text, so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('user explicitly asks the platform team to write an article and accepts the cost'), explicit when-not ('user brings their own text: use create_article'), plus a hard prerequisite (AI assistant toggle must be on). Nothing is left to inference.

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

All Comunicate.top 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.