Skip to main content
Glama

Actualizează pe site (cerere de aprobare)

request_site_update
DestructiveIdempotent

Butonul „Actualizează pe site" din cont: trimite echipei Comunicate.eu cererea ca articolul deja publicat să fie înlocuit pe site cu versiunea salvată acum în platformă. Întâi salvează schimbarea cu update_article; aici doar ceri aplicarea ei. Nu costă nimic. Textul de pe site se schimbă abia după ce echipa aprobă cererea — spune-i asta omului, nu-i spune că s-a modificat deja.

Use when an already published article was changed with update_article and the user wants the change on the site (the „Actualizează pe site” button). Do not use for a new publication: use order_publication. The change goes live only after the Comunicate.eu team approves it.

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": {
      "publicationId": "<publicationId>",
      "reason": "<reason>"
    },
    "name": "request_site_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesCe s-a schimbat și de ce, pe scurt (minim 10 caractere): echipa îl citește când aprobă.
publicationIdYesPublicarea de actualizat, din list_publications sau get_publication (nu id-ul articolului).

Output Schema

NameRequiredDescriptionDefault
idNostring. The change request.
notaNostring. What happens next; say it to the user.
statusNostring. PENDING until the team approves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses the key behaviors: the request is free, the change does not go live until the Comunicate.eu team approves it, and the agent must tell the user it is pending rather than done. This resolves the practical meaning of destructiveHint=true (eventual replacement, not immediate mutation) and adds an approval-gating trait the annotations cannot express.

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

Conciseness3/5

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

The front-loaded instruction about invoking the 'Actualizează pe site' button is well placed, but the text is effectively written twice — once in Romanian and once in English — restating the same approval and alternative-tool facts. Useful for a bilingual audience, but it doubles the length without adding information.

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?

With an output schema present and full schema coverage, the description only needs to cover intent, prerequisites, and user-facing behavior — all of which it does, including what to tell the user. The only shortfall is that nothing is said about what happens if the team rejects the request or how the agent would learn the outcome.

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 both parameters already document themselves, including the note that publicationId is the publication id and not the article id. The description adds no parameter-level detail beyond that, 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?

The description names a specific verb and resource: it submits a request to Comunicate.eu to replace an already-published article on the site with the version currently saved in the platform. It explicitly distinguishes this from update_article (which saves the change) and from order_publication (new publication), so an agent can tell the three apart 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 use condition (an already published article was changed with update_article and the user wants it on the site), an explicit precondition (save first with update_article), and an explicit exclusion with the named alternative (new publication → order_publication). Nothing about when to select this tool 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.