Comunicate.top

Un site din catalog

get_site

Read-onlyIdempotent

Detaliile unui site după id: prețuri și linkuri pe tip de campanie, reguli, condițiile publicației dacă are. Merge fără cont; cu cheie arată și cum ar plăti organizația.

Use when you have a site id and need its prices per campaign type, link terms and rules before ordering. Do not use for browsing many sites: use search_catalog.

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": {
      "siteId": "<siteId>"
    },
    "name": "get_site"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes	Site-ul, din search_catalog, get_niche sau plan_budget.

Output Schema

Name	Required	Description
`da`	No	number
`dr`	No	number
`id`	No	string
`url`	No	string
`name`	No	string
`niches`	No	array of string
`payment`	No	object. With an account: whether a package or the balance can pay for it.
`refuzaTextAi`	No	boolean. True when the site only accepts text rewritten by a person.
`reguliGenerale`	No	string. Site rules.
`maxLinksByCampaign`	No	object. Most links allowed per campaign type.
`linkPolicyByCampaign`	No	object. Link attribute per campaign type.
`priceCentsByCampaign`	No	object. Price per campaign type, in cents, VAT excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026

removedInput schema / $schema

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

changedInput schema / properties / siteId / description

Previous value: -"Id-ul site-ului (UUID), din search_catalog, get_niche sau plan_budget."New value: +"Site-ul, din search_catalog, get_niche sau plan_budget."

removedInput schema / properties / siteId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "da": {
+      "description": "number"
+    },
+    "dr": {
+      "description": "number"
+    },
+    "id": {
+      "description": "string"
+    },
+    "linkPolicyByCampaign": {
+      "description": "object. Link attribute per campaign type."
+    },
+    "maxLinksByCampaign": {
+      "description": "object. Most links allowed per campaign type."
+    },
+    "name": {
+      "description": "string"
+    },
+    "niches": {
+      "description": "array of string"
+    },
+    "payment": {
+      "description": "object. With an account: whether a package or the balance can pay for it."
+    },
+    "priceCentsByCampaign": {
+      "description": "object. Price per campaign type, in cents, VAT excluded."
+    },
+    "refuzaTextAi": {
+      "description": "boolean. True when the site only accepts text rewritten by a person."
+    },
+    "reguliGenerale": {
+      "description": "string. Site rules."
+    },
+    "url": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 7, 2026
- addedInput schema / properties / siteId / description
```
Added value: +"Id-ul site-ului (UUID), din search_catalog, get_niche sau plan_budget."
```

Changed2 schema fields changedNov 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / siteId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context about authentication modes: it works without an account, and with a key it additionally reveals how the organization would pay. It does not discuss rate limits or data staleness, but the auth-mode disclosure is the kind of behavioral detail annotations cannot carry.

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 resource and payload, then the usage rule and exclusion; no filler sentences. It mixes Romanian and English in one paragraph, which is slightly jarring but does not cost any information density.

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-value shape need not be described, and the description still summarizes the payload categories plus the auth-dependent difference in response. For a one-parameter read tool this is close to complete; only edge cases such as unknown or unpublished site ids are unaddressed.

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 coverage is 100% and the single siteId parameter already documents its provenance (from search_catalog, get_niche or plan_budget). The description only restates that lookup is by id, adding no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

Names a specific resource and retrieval key ('detaliile unui site după id') and enumerates exactly what comes back: prices and links per campaign type, rules, and publication conditions. It is unmistakably distinct from listing/browsing tools like search_catalog.

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: 'you have a site id and need its prices per campaign type, link terms and rules before ordering', and an explicit when-not with a named alternative: 'Do not use for browsing many sites: use search_catalog.' Nothing is left 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.