Skip to main content
Glama

Leadgen ONRC Romania

by com.adrianhomelab
OverviewAdmin

watch_company

Register a company (by CUI) to watch for registry changes.

Stores a fingerprint of the firm's current ONRC record as the baseline.
poll_watchlist then reports the firm whenever its record changes between
monthly ONRC snapshots (new director, new CAEN activity, address/status
change...). Diacritic-insensitive throughout; CUI is exact.

Args:
    cui: Romanian tax identification number (CUI) of the firm to watch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cuiYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Explains the side effect of storing a baseline fingerprint and that future changes are reported via poll_watchlist. It also notes diacritic-insensitivity and exact CUI matching, giving useful behavioral context beyond the bare action.

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

Conciseness5/5

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

The description is compact and free of fluff, using short paragraphs to convey purpose, persistence behavior, and parameter meaning. Every sentence adds relevant 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?

Covers the essential action, the stored state, the follow-up via poll_watchlist, and the input format. It does not mention the return value, but for a simple registration tool this is not a critical omission.

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

Parameters5/5

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

The only parameter, cui, is fully explained as a Romanian tax identification number for the firm to watch. The description provides sufficient semantic detail despite the schema lacking a property-level description.

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?

Clearly states the verb 'register', the resource 'company', and the purpose 'to watch for registry changes'. It is immediately distinguishable from siblings like poll_watchlist and watch_caen.

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

Usage Guidelines3/5

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

Implies usage by specifying the CUI identifier and describing the downstream poll_watchlist behavior, but it does not explicitly state when to choose this tool over alternatives such as watch_caen.

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

All Leadgen ONRC Romania toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources