Skip to main content
Glama
Sign In

Comunicate.top

by top.comunicate
OverviewDiscussionsAdmin

Cifrele catalogului

catalog_stats
Read-onlyIdempotent

Câte publicații sunt în catalog și alte cifre generale. Merge fără cont.

Use when the user asks how big the catalogue is or wants headline figures. Do not use when looking for specific publications: use 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": "catalog_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nichesNonumber. Niches (topics).
publicationsNonumber. Active publications in the catalogue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "niches": {
+      "description": "number. Niches (topics)."
+    },
+    "publications": {
+      "description": "number. Active publications in the catalogue."
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds a genuinely non-obvious behavioral fact beyond that: 'Merge fără cont' — it works without an account, which matters for auth handling and confirms the figures are global rather than account-scoped. It does not add rate-limit or freshness/staleness details, so it stops short of a 5.

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 structure is front-loaded and efficient: a one-line statement of what it returns, then a compact use/don't-use pair. The Romanian opening sentence is largely restated by the English usage line, a minor redundancy, but no sentence is wasted and the total length is proportionate to a no-argument stats tool.

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 zero parameters, an output schema covering return values, and annotations covering safety and idempotency, the remaining gaps an agent faces are purpose, routing and auth — all three are addressed. Nothing needed to call this tool correctly 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made that could conflict with the empty schema.

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 concrete resource and metric: how many publications are in the catalogue plus other headline figures, and it explicitly separates this from search_catalog and plan_budget. The phrase 'alte cifre generale' ('other general figures') stays vague about which additional metrics are returned, and the bilingual phrasing (Romanian lead sentence) slightly blunts immediate clarity for an English-speaking agent.

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 both a positive trigger ('when the user asks how big the catalogue is or wants headline figures') and an explicit exclusion ('Do not use when looking for specific publications'), then names the two sibling tools to use instead. This is exactly the routing information an agent needs to choose among catalog-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Comunicate.top toolsInspect
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.

Resources