Skip to main content
Glama
edithatogo

fyi-mcp

by edithatogo
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Sync Monitor

sync_monitor
Read-onlyIdempotent

Summarize offline synchronization health including clean/dirty/conflict counts, queue depth, latest sync time, and degradation indicators. Read-only operations overview.

Instructions

Summarize offline synchronization health: clean/dirty/conflict request counts, outgoing queue depth, latest sync time, and offline degradation indicators. Use for an operations overview; prefer sync_status for one request, sync_conflicts to list conflicted rows, and check_status for database connectivity/record totals. Read-only and idempotent; does not start a sync job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
syncYesAggregate request sync counts and latest sync timestamp.
queueYesOutgoing offline queue counts by pending, submitted, and failed status.
offline_degradationYesOperational indicators showing queued local changes and dirty records.

Schema Changelog

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

  1. Changed12 schema fields changedv0.1.1
    • addedOutput schema / properties / offline_degradation / additionalProperties
      Added value: +false
    • addedOutput schema / properties / offline_degradation / description
      Added value: +"Operational indicators showing queued local changes and dirty records."
    • addedOutput schema / properties / offline_degradation / properties
      Added value: +{
+  "dirty_records": {
+    "description": "Requests with unsynced local changes.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "queued_changes": {
+    "description": "Pending plus failed outgoing queue entries.",
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • addedOutput schema / properties / offline_degradation / required
      Added value: +[
+  "queued_changes",
+  "dirty_records"
+]
    • addedOutput schema / properties / queue / additionalProperties
      Added value: +false
    • addedOutput schema / properties / queue / description
      Added value: +"Outgoing offline queue counts by pending, submitted, and failed status."
    • addedOutput schema / properties / queue / properties
      Added value: +{
+  "failed": {
+    "description": "Outgoing queue entries that failed submission.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "pending": {
+    "description": "Outgoing queue entries waiting to be submitted.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "submitted": {
+    "description": "Outgoing queue entries already submitted.",
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • addedOutput schema / properties / queue / required
      Added value: +[
+  "pending",
+  "submitted",
+  "failed"
+]
    • addedOutput schema / properties / sync / additionalProperties
      Added value: +false
    • addedOutput schema / properties / sync / description
      Added value: +"Aggregate request sync counts and latest sync timestamp."
    • addedOutput schema / properties / sync / properties
      Added value: +{
+  "clean": {
+    "description": "Requests known to be cleanly synchronized.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "conflict": {
+    "description": "Requests with unresolved sync conflicts.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "dirty": {
+    "description": "Requests with unsynced local changes.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "latest_sync": {
+    "description": "Most recent successful synchronization timestamp.",
+    "format": "date-time",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "pending": {
+    "description": "Requests pending synchronization.",
+    "minimum": 0,
+    "type": "integer"
+  },
+  "total": {
+    "description": "Total number of requests tracked by sync metadata.",
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • addedOutput schema / properties / sync / required
      Added value: +[
+  "total",
+  "clean",
+  "dirty",
+  "pending",
+  "conflict",
+  "latest_sync"
+]
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint=false. Description adds 'does not start a sync job' and reinforces read-only, idempotent nature, providing context beyond annotations without contradiction.

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?

Two sentences, front-loaded with key information (purpose, output list), followed by usage guidance. Every sentence is essential and concise.

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 zero parameters, a rich output schema, and 13 siblings, the description covers purpose, usage, behavioral traits, and sibling differentiation completely. No gaps remain.

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

Parameters4/5

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

No parameters exist, so the description correctly omits parameter details. The schema covers 100% with no properties. The description adds value by listing the output fields, which is sufficient.

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 summarizes offline synchronization health with specific metrics (clean/dirty/conflict counts, queue depth, latest sync time, degradation indicators). It distinguishes from siblings sync_status, sync_conflicts, and check_status.

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?

Explicitly states when to use ('operations overview') and when not to, recommending alternatives for different tasks (sync_status for one request, sync_conflicts for conflicts, check_status for connectivity/totals).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/edithatogo/fyi-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server