Comunicate.top

Nișele

list_niches

Read-onlyIdempotent

Nișele catalogului, cu descriere și numărul de publicații. publicationCount numără toate limbile și tipurile de campanie, deci pe un tip și o limbă sunt mai puține. Merge fără cont.

Use when you need the valid niche slugs or want to show the user which topics the catalogue covers. Do not use when you already know the niche: pass it directly to search_catalog or plan_budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_niches"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No	Limba textelor: ro (implicit) sau en.

Output Schema

Name	Required	Description	Default
`items`	No	array of {slug, name, description, publicationCount, averageDa}. Pass `slug` as `niche` to other tools.

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": {
+    "items": {
+      "description": "array of {slug, name, description, publicationCount, averageDa}. Pass `slug` as `niche` to other tools."
+    }
+  },
+  "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
```
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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words elsewhere: it discloses that the call works without an account and warns that publicationCount aggregates all languages and campaign types, so per-type/per-language counts will be lower. That counting caveat is genuinely useful context an agent could not get from the schema.

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?

The content is front-loaded and every clause carries information: resource, count caveat, auth note, use case, exclusion. The only friction is the language switch, with the resource description in Romanian and the usage guidance in English, which reads slightly disjointed but is not wasteful.

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?

With an output schema present, annotations covering the read-only/idempotent profile, and a single optional enum parameter, the description supplies everything remaining: scope, the account-free access, and the count-aggregation caveat. Nothing an agent needs in order to call it correctly or interpret the counts 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 the single locale parameter already has an enum plus a Romanian explanation of its default. The description adds no further information about locale or how it affects the returned niche names/descriptions, so the baseline of 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?

The description states a specific verb+resource: it lists the catalogue's niches together with their description and publication count, so an agent knows exactly what comes back. It does not name the closely related sibling get_niche, so differentiation from that tool relies on the reader inferring it from the 'do not use when you already know the niche' clause.

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?

It gives an explicit use case ('when you need the valid niche slugs or want to show the user which topics the catalogue covers') and an explicit exclusion plus redirect ('Do not use when you already know the niche: pass it directly to search_catalog or plan_budget'). The agent has both a trigger and an alternative path, leaving little 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.