Skip to main content
Glama
edithatogo

fyi-mcp

by edithatogo
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Sync Status

sync_status
Read-onlyIdempotent

Get aggregate counts of clean, dirty, pending, and conflict sync statuses, or check the last synced timestamp for a specific request. Read-only and idempotent.

Instructions

Read offline-sync metadata either as aggregate counts (omit request_id) or for one request (provide request_id). Use when you need clean/dirty/pending/conflict numbers or per-request last_synced timestamps; use sync_monitor for queue depth + offline degradation, sync_conflicts for conflicted rows only, and check_status for database health. Read-only and idempotent; does not mutate state or trigger network sync.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idNoOptional local request ID. Omit for aggregate counts; set to load that request's sync_status, last_synced_at, and conflict_version.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed7 schema fields changedv0.1.1
    • changedInput schema / properties / request_id / description
      Previous value: -"Optional request ID for per-request sync metadata."New value: +"Optional local request ID. Omit for aggregate counts; set to load that request's sync_status, last_synced_at, and conflict_version."
    • addedInput schema / properties / request_id / minimum
      Added value: +1
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +false
    • changedOutput schema / description
      Previous value: -"Synchronization metadata."New value: +"Synchronization metadata. Aggregate counts are returned when request_id is omitted; per-request metadata is returned when request_id is provided."
    • addedOutput schema / oneOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "description": "Aggregate offline synchronization counts.",
+    "properties": {
+      "clean": {
+        "description": "Number of requests with clean sync metadata.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "conflict": {
+        "description": "Number of requests currently in conflict.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "dirty": {
+        "description": "Number of requests with unsynced local changes.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "pending": {
+        "description": "Number of requests queued or pending sync.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "total": {
+        "description": "Total number of requests represented in aggregate sync status.",
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "total",
+      "clean",
+      "dirty",
+      "pending",
+      "conflict"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Per-request offline synchronization metadata.",
+    "properties": {
+      "conflict_version": {
+        "description": "Conflict version counter when a sync conflict has been detected.",
+        "minimum": 0,
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "last_synced_at": {
+        "description": "Last successful sync timestamp for this request.",
+        "format": "date-time",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "local_updated_at": {
+        "description": "Last local update timestamp known for this request.",
+        "format": "date-time",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "remote_updated_at": {
+        "description": "Last remote update timestamp known for this request.",
+        "format": "date-time",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "request_id": {
+        "description": "Request ID for the per-request sync lookup.",
+        "minimum": 1,
+        "type": "integer"
+      },
+      "sync_status": {
+        "description": "Per-request sync status, or null when that request has no sync metadata.",
+        "enum": [
+          "clean",
+          "dirty",
+          "pending",
+          "conflict",
+          null
+        ],
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "request_id",
+      "sync_status"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "request_id": {
-    "type": "integer"
-  },
-  "sync_status": {
-    "type": [
-      "string",
-      "null"
-    ]
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "request_id",
-  "sync_status"
-]
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds 'does not mutate state or trigger network sync', providing extra behavioral context beyond annotations.

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?

Three concise sentences, no wasted words. Purpose is front-loaded, and every sentence adds value.

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?

With annotations and output schema, description fully covers the tool's behavior, usage modes, safety profile, and ties to sibling tools. Nothing missing.

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?

Only one parameter (request_id) with 100% schema coverage. Description adds critical semantics: omit for aggregate counts, provide for per-request details including specific fields (sync_status, last_synced_at, conflict_version).

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?

Description specifies verb 'Read', resource 'offline-sync metadata', and two modes (aggregate or per-request). It clearly distinguishes from sibling tools like sync_monitor, 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 ('Use when you need clean/dirty/pending/conflict numbers or per-request last_synced timestamps') and provides specific alternatives for related tasks, leaving no ambiguity.

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