Skip to main content
Glama

dd

by dev.cz-agents

Watch Czech Company

watch_entity
Read-only

Start onboarding for free monitoring of one Czech company by IČO. Stub only — persists nothing yet. Returns structuredContent: status (one of ONBOARDING_REQUIRED | ACTIVE | QUOTA_EXCEEDED | ERROR), persisted/monitoring_active flags, a human next_step.url for onboarding (the user completes onboarding + GDPR consent themselves — do not open the link or submit data on their behalf), and pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icoYesCzech IČO — 7 or 8 digits.

Schema Changelog

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

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "agent_guidance": {
-      "type": "string"
-    },
-    "delivery_channel": {
-      "type": "null"
-    },
-    "free_quota": {
-      "additionalProperties": false,
-      "properties": {
-        "limit": {
-          "type": "number"
-        },
-        "used": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "limit",
-        "used"
-      ],
-      "type": "object"
-    },
-    "ico": {
-      "type": "string"
-    },
-    "locale": {
-      "const": "cs",
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "monitoring_active": {
-      "type": "boolean"
-    },
-    "next_step": {
-      "additionalProperties": false,
-      "properties": {
-        "action": {
-          "const": "complete_onboarding",
-          "type": "string"
-        },
-        "actor": {
-          "const": "human",
-          "type": "string"
-        },
-        "requires": {
-          "items": {
-            "enum": [
-              "notification_channel",
-              "gdpr_consent"
-            ],
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "url": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "actor",
-        "action",
-        "url",
-        "requires"
-      ],
-      "type": "object"
-    },
-    "persisted": {
-      "type": "boolean"
-    },
-    "pricing": {
-      "additionalProperties": false,
-      "properties": {
-        "solo": {
-          "type": "string"
-        },
-        "team": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "solo",
-        "team"
-      ],
-      "type": "object"
-    },
-    "schema_version": {
-      "const": 1,
-      "type": "number"
-    },
-    "status": {
-      "enum": [
-        "ONBOARDING_REQUIRED",
-        "ACTIVE",
-        "QUOTA_EXCEEDED",
-        "ERROR"
-      ],
-      "type": "string"
-    },
-    "tier": {
-      "const": "free",
-      "type": "string"
-    }
-  },
-  "required": [
-    "schema_version",
-    "status",
-    "persisted",
-    "monitoring_active",
-    "ico",
-    "tier",
-    "free_quota",
-    "delivery_channel",
-    "next_step",
-    "agent_guidance",
-    "pricing",
-    "message",
-    "locale"
-  ],
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "agent_guidance": {
+      "type": "string"
+    },
+    "delivery_channel": {
+      "type": "null"
+    },
+    "free_quota": {
+      "additionalProperties": false,
+      "properties": {
+        "limit": {
+          "type": "number"
+        },
+        "used": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "limit",
+        "used"
+      ],
+      "type": "object"
+    },
+    "ico": {
+      "type": "string"
+    },
+    "locale": {
+      "const": "cs",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "monitoring_active": {
+      "type": "boolean"
+    },
+    "next_step": {
+      "additionalProperties": false,
+      "properties": {
+        "action": {
+          "const": "complete_onboarding",
+          "type": "string"
+        },
+        "actor": {
+          "const": "human",
+          "type": "string"
+        },
+        "requires": {
+          "items": {
+            "enum": [
+              "notification_channel",
+              "gdpr_consent"
+            ],
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "actor",
+        "action",
+        "url",
+        "requires"
+      ],
+      "type": "object"
+    },
+    "persisted": {
+      "type": "boolean"
+    },
+    "pricing": {
+      "additionalProperties": false,
+      "properties": {
+        "solo": {
+          "type": "string"
+        },
+        "team": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "solo",
+        "team"
+      ],
+      "type": "object"
+    },
+    "schema_version": {
+      "const": 1,
+      "type": "number"
+    },
+    "status": {
+      "enum": [
+        "ONBOARDING_REQUIRED",
+        "ACTIVE",
+        "QUOTA_EXCEEDED",
+        "ERROR"
+      ],
+      "type": "string"
+    },
+    "tier": {
+      "const": "free",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "status",
+    "persisted",
+    "monitoring_active",
+    "ico",
+    "tier",
+    "free_quota",
+    "delivery_channel",
+    "next_step",
+    "agent_guidance",
+    "pricing",
+    "message",
+    "locale"
+  ],
+  "type": "object"
+}
  5. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: it's a stub that persists nothing, returns specific statuses and flags, and instructs the agent not to open the onboarding link or submit data on the user's behalf. This is exactly the kind of context annotations cannot capture.

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 two sentences, front-loaded with purpose, and every clause adds value: stub status, return payload, and user responsibility. No fluff or repetition.

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?

Given the simple schema and lack of output schema, the description fully explains return values (status enum, flags, next_step.url, pricing) and clarifies the manual onboarding step. This is complete for an MCP tool with one parameter.

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% with the 'ico' parameter already described as 'Czech IČO — 7 or 8 digits.' The description adds no further parameter details; the baseline of 3 applies because the schema carries the burden and the description doesn't undercut or enrich it.

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 clearly states the tool's purpose: starting onboarding for monitoring a Czech company by IČO. It uses a specific verb ('Start onboarding') and resource ('monitoring of one Czech company'), and distinguishes itself from sibling detection/report tools by focusing on the watch/onboarding flow.

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 context implies when to use (user wants to monitor a company), and sibling tools are clearly different (detection reports, ownership lookup). However, it lacks explicit exclusions or alternatives, so it doesn't fully meet the 'explicit alternatives' bar.

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

All dd 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.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: address crowding, nominee directors, phoenix patterns, owners, statutory chains, timelines, and watch functionality are all separate. However, get_dd_report and get_risk_score overlap significantly (full report vs. just the score), and the three detect_* tools share a similar pattern but apply to different risk types.

Naming Consistency4/5

Tool names predominantly follow a verb_noun pattern (detect_, get_, watch_), but person_companies breaks this convention (noun_noun). The mix of detect_ and get_ verbs is consistent within their respective semantic groups, making the overall pattern readable.

Tool Count5/5

With 12 tools, the server is well-scoped for a due-diligence domain. Each tool addresses a distinct aspect (risk detection, reports, ownership, monitoring) without unnecessary bloat, and the count sits comfortably within the ideal range.

Completeness4/5

The server covers the core due-diligence lifecycle reasonably well: company facts, risk scoring, timeline, ownership, EU lookup, and monitoring onboarding. Minor gaps exist—watch_entity is a stub, and advanced features are explicitly deferred to a companion server (ddplus)—but these are acknowledged and don't break the primary workflows.

Resources