Comunicate.eu

Articolele organizației

list_articles

Read-onlyIdempotent

Lista articolelor (ciorne și publicate), paginată.

Use when the user asks about their drafts or articles, or you need an article id. Do not use when you already have the id: use get_article.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Câte rezultate pe pagină. Ex.: 10
`cursor`	No	De unde continuă lista: valoarea `nextCursor` din răspunsul anterior. Lipsă sau 0 = prima pagină.

Output Schema

Name	Required	Description	Default
`items`	No	array of {id, title, status, version}. Drafts and articles of the organisation.
`nextCursor`	No	number\|string\|null. Pass it as `cursor` to get the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026

removedInput schema / $schema

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

removedInput schema / properties / cursor / maximum
```
Removed value: -9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "items": {
+      "description": "array of {id, title, status, version}. Drafts and articles of the organisation."
+    },
+    "nextCursor": {
+      "description": "number|string|null. Pass it as `cursor` to get the next page; null on the last page."
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedNov 7, 2026

addedInput schema / properties / cursor / description

Added value: +"De unde continuă lista: valoarea `nextCursor` din răspunsul anterior. Lipsă sau 0 = prima pagină."

addedInput schema / properties / limit / description

Added value: +"Câte rezultate pe pagină. Ex.: 10"

Changed2 schema fields changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / cursor / maximum
```
Added value: +9007199254740991
```
First observedOct 31, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description's only added behavioral fact is that the listing includes both drafts and published items, which is useful scope information but modest. It says nothing about ordering, page size limits, or rate limits.

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

Conciseness5/5

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

Two sentences, no filler, and the core capability plus the routing constraint are front-loaded. Every clause carries information the agent needs.

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?

An output schema exists, so return-shape explanation is unnecessary, and both optional parameters are fully described in the schema. What remains thin is ordering and page-size defaults, which the description leaves entirely to the schema. For a simple two-parameter list tool this is close to complete.

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 both limit and cursor are already documented in the schema, including the cursor convention referencing nextCursor. The description only mentions that the list is paginated, adding no syntax or semantics beyond the schema. 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list articles), the scope of what is returned (drafts and published), and the pagination behavior. It also names the sibling get_article as the contrasting tool, so an agent can distinguish the two without opening a 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?

Gives an explicit when-to-use clause ('user asks about their drafts or articles, or you need an article id') and an explicit when-not clause with the alternative named ('Do not use when you already have the id: use get_article'). This is the full 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.eu 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.