Comunicate.top

O publicație din rețeaua proprie

get_own_publication

Read-onlyIdempotent

Detaliile unei publicații din rețeaua proprie, cu rubricile ei. Merge fără cont.

Use when the user asks about one publication of the own network, by its slug from list_own_network. Do not use for other catalogue sites: use get_site with the site id.

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": {
      "slug": "<slug>"
    },
    "name": "get_own_publication"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Slug-ul publicației din list_own_network: domeniul cu cratime. Ex.: topantreprenor-ro
`locale`	No	Limba textelor: ro (implicit) sau en.

Output Schema

Name	Required	Description
`url`	No	string
`name`	No	string
`slug`	No	string
`terms`	No	array. Price, link policy and turnaround per campaign type.
`niches`	No	array of string
`topics`	No	array of string. Editorial sections.
`marking`	No	string. How the publication labels paid content.
`metricDa`	No	number
`metricDr`	No	number
`description`	No	string

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

removedInput schema / $schema

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "description": {
+      "description": "string"
+    },
+    "marking": {
+      "description": "string. How the publication labels paid content."
+    },
+    "metricDa": {
+      "description": "number"
+    },
+    "metricDr": {
+      "description": "number"
+    },
+    "name": {
+      "description": "string"
+    },
+    "niches": {
+      "description": "array of string"
+    },
+    "slug": {
+      "description": "string"
+    },
+    "terms": {
+      "description": "array. Price, link policy and turnaround per campaign type."
+    },
+    "topics": {
+      "description": "array of string. Editorial sections."
+    },
+    "url": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedNov 7, 2026

addedInput schema / properties / locale / description

Added value: +"Limba textelor: ro (implicit) sau en."

addedInput schema / properties / slug / description

Added value: +"Slug-ul publicației din list_own_network: domeniul cu cratime. Ex.: topantreprenor-ro"

Changed1 schema field changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious operational fact not in the annotations: 'Merge fără cont' (it works without an account), which tells the agent no authentication is required. It says nothing about rate limits or payload size, but with an output schema present that is a minor omission.

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?

Two short sentences, with the resource detail front-loaded and the routing instruction second. The mixed Romanian/English phrasing duplicates the 'own network' concept across the two sentences, but nothing is padded and the structure is clear.

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?

With an output schema covering return values, full schema descriptions, and annotations covering the safety profile, the description supplies what is left: no-auth behavior and the slug's provenance. The one real hole is that it does not explain how this differs from get_publication, which matters given how many sibling tools exist.

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 100%: the slug parameter is documented with length bounds and a concrete example ('topantreprenor-ro'), and locale has an enum with a stated default. The description adds only one thing beyond the schema, that the slug comes from list_own_network, so the baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: fetching the details ('Detaliile') of one publication in the own network, including its sections ('rubricile'). It explicitly excludes other catalogue sites and points to get_site, which helps. However, it never distinguishes itself from the sibling get_publication, which an agent will also see in the tool list and could easily confuse with this one.

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

Usage Guidelines4/5

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

There is explicit when-to-use guidance ('Use when the user asks about one publication of the own network, by its slug from list_own_network') plus a when-not with a named alternative ('Do not use for other catalogue sites: use get_site'). The only gap is that the relationship to get_publication, the most likely confusing sibling, is left unexplained.

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.