Comunicate.top

Rezumatul unei perioade

report_summary

Read-onlyIdempotent

Publicări, reușite, eșuate, site-uri distincte, credite și bani cheltuiți într-un interval (implicit ultimele 30 de zile).

Use when the user asks for totals over a period: publications, failures, sites, credits and money spent. Do not use for one publication: use get_publication.

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": "report_summary"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	YYYY-MM-DD
`from`	No	YYYY-MM-DD

Output Schema

Name	Required	Description
`to`	No	string
`from`	No	string
`failed`	No	number
`published`	No	number
`creditsUsed`	No	number
`successRate`	No	number. Between 0 and 1.
`publications`	No	number
`distinctSites`	No	number
`moneySpentCents`	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": {
+    "creditsUsed": {
+      "description": "number"
+    },
+    "distinctSites": {
+      "description": "number"
+    },
+    "failed": {
+      "description": "number"
+    },
+    "from": {
+      "description": "string"
+    },
+    "moneySpentCents": {
+      "description": "number"
+    },
+    "publications": {
+      "description": "number"
+    },
+    "published": {
+      "description": "number"
+    },
+    "successRate": {
+      "description": "number. Between 0 and 1."
+    },
+    "to": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

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

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds a genuinely useful behavioral fact not in the schema or annotations: the interval defaults to the last 30 days when omitted. It stops short of stating whether boundaries are inclusive or which timezone applies, so it is strong but not exhaustive.

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 compact sentences with the metric list front-loaded and the exclusion last, so there is no wasted preamble. Minor deduction: the opening Romanian sentence restates the same metric list as the English guidance, and the default-range fact is buried there in a different language than the rest of the text.

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?

An output schema exists, so return-value explanation is unnecessary, and all four annotations plus full schema coverage carry the structural burden. With zero required parameters, a defaulted range, and a named alternative, nothing an agent needs in order to select and invoke this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents both params as YYYY-MM-DD, so the baseline is 3. The description earns above-baseline credit by explaining that both optional parameters have a defaulted range (last 30 days), which is semantics the schema does not express.

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 names a specific aggregate resource set — publications, successes, failures, distinct sites, credits and money spent over an interval — and explicitly separates it from the single-record sibling get_publication. An agent can distinguish it from list_publications or catalog_stats without opening any 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?

It gives an explicit when-to-use condition (user asks for totals over a period) and an explicit when-not with a named alternative ("Do not use for one publication: use get_publication"). Both the positive and negative routing are covered.

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.