Comunicate.top

O nișă

get_niche

Read-onlyIdempotent

Descrierea unei nișe și cele mai puternice 5 publicații din ea, cu id. Merge fără cont.

Use when the user asks about one topic (what it covers, typical publications). Do not use when the user wants a priced selection for a budget: use plan_budget.

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_niche"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Slug sau nume de nișă (ex. sanatate, business)
`locale`	No	Limba textelor: ro (implicit) sau en.

Output Schema

Name	Required	Description
`name`	No	string
`slug`	No	string. Niche id.
`exemple`	No	array. Sample Romanian publications: domain, DA, price, turnaround.
`averageDa`	No	number. Average Domain Authority.
`description`	No	string
`publicationCount`	No	number

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": {
+    "averageDa": {
+      "description": "number. Average Domain Authority."
+    },
+    "description": {
+      "description": "string"
+    },
+    "exemple": {
+      "description": "array. Sample Romanian publications: domain, DA, price, turnaround."
+    },
+    "name": {
+      "description": "string"
+    },
+    "publicationCount": {
+      "description": "number"
+    },
+    "slug": {
+      "description": "string. Niche id."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 7, 2026
- addedInput schema / properties / locale / description
```
Added value: +"Limba textelor: ro (implicit) sau en."
```
Changed1 schema field changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / slug / description

Previous value: -"Slug sau nume din list_niches"New value: +"Slug sau nume de nișă (ex. sanatate, business)"

Changed1 schema field changedOct 31, 2026
- addedInput schema / properties / slug / description
```
Added value: +"Slug sau nume din list_niches"
```
First observedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely useful behavioral fact not in the annotations: it works without an account, which tells the agent no auth step is needed before calling it. It says nothing about pagination or response shape, but an output schema exists to cover that.

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 return contents, then the routing rules in two short sentences with no filler. Minor friction comes from the Romanian/English mix within one description and the slightly ambiguous trailing 'cu id', which requires a beat to parse.

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

Completeness5/5

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

For a simple two-parameter read, the description covers what is returned, the auth requirement, when to use it, and which sibling to use instead, while annotations cover safety and the output schema covers return structure. Nothing an agent needs in order to call it correctly is missing.

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% and both parameters (slug, locale) are documented in the schema with examples and the default language. The description adds no extra meaning about slug formats or locale behavior, 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?

States a specific verb+resource: it returns a niche's description plus its top 5 publications with ids, which is information the name get_niche alone does not convey. Implicitly separated from the catalog-listing siblings (list_niches) by 'una dintre nișe' framing, though that sibling is never named explicitly.

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?

Both directions are spelled out: use when the user asks about one topic (coverage, typical publications), and explicitly do not use when the user wants a priced selection for a budget, routing them to plan_budget instead. This is exactly the when/when-not/alternative pattern.

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.