Skip to main content
Glama
Sign In

LICHIDARE.MD

by md.lichidare
OverviewDiscussionsAdmin

Link pentru alerte despre loturi noi

alert_subscription_link
Read-only

Intoarce linkul catre formularul de alerte LICHIDARE.MD, plus canalul Telegram. Doua feluri: (1) dupa o categorie, o procedura si o regiune: catalogul filtrat cu formularul deschis si criteriile deja selectate; (2) dupa un VANZATOR anume (executor, administrator autorizat, banca, SFS, primarie), parametrul seller cu numele lui: formularul de abonare la anunturile acestui vanzator, cu vanzatorul deja completat. Vanzatorul se recunoaste exact dupa nume (nu dupa fragment); daca numele nu e gasit, pagina spune asta. Abonarea pe vanzator primeste doar loturile in care el este vanzatorul, nu cele in care e doar mentionat (de exemplu creditor). Utilizatorul introduce doar adresa de e-mail, bifeaza acordul si confirma abonarea din e-mail. Instrumentul nu trimite si nu stocheaza nicio adresa de e-mail.

Input Schema

NameRequiredDescriptionDefault
regionNoRaion sau municipiu, ex. 'Chisinau', 'Balti', 'Nisporeni', 'Stefan Voda'
sellerNoNumele vanzatorului, asa cum apare pe anunt (ex. Prutean Viorica, MAIB S.A., Serviciul Fiscal de Stat). Cand e dat, linkul duce la abonarea pe acest vanzator; categoria, procedura si regiunea nu se aplica.
categoryNoimobile (inclusiv terenuri), transport, echipament (industrial/agricol) sau alte bunuri
procedureNoProcedura de vanzare: insolvabilitate, executare_silita, gaj_bancar, sfs (bunuri confiscate), apl (primarii), alta

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / seller
      Added value: +{
+  "description": "Numele vanzatorului, asa cum apare pe anunt (ex. Prutean Viorica, MAIB S.A., Serviciul Fiscal de Stat). Cand e dat, linkul duce la abonarea pe acest vanzator; categoria, procedura si regiunea nu se aplica.",
+  "maxLength": 120,
+  "minLength": 3,
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses important behavior: seller matching is exact by name (not fragment) with a defined fallback when not found, seller subscriptions only include lots where that party is the seller (not merely mentioned as creditor), and the user completes the subscription by email while the tool neither sends nor stores any address. This is exactly the kind of context 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?

It is front-loaded with the core outcome and organized around the two modes, with each sentence carrying substance. It is a dense single block and slightly repetitive on the email/privacy point, which prevents a 5.

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?

For a 4-optional-param tool with no output schema, the description conveys what is returned (a link plus Telegram channel) and the key edge cases. It does not describe the shape of the returned value (e.g., fields), a minor gap for an otherwise simple, well-covered tool.

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%, so all four parameters (including both enums) are already documented. The description restates the seller precedence and exact-match rule that the schema also contains, adding little beyond structured data, 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 first sentence states a specific verb and resource: it returns the link to the LICHIDARE.MD alert form plus the Telegram channel. It then enumerates the two modes (filtered catalog vs. seller-specific), so an agent can immediately tell this apart from search_listings or get_listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly explains the two usage modes and the precedence rule that when 'seller' is supplied the category/procedure/region parameters do not apply. It lacks explicit guidance on when to pick this tool over the sibling listing tools (e.g., 'use this after searching to subscribe'), which keeps it from a 5.

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

All LICHIDARE.MD 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