Skip to main content
Glama
inboxd
by 47star

sync_status

Check collector health, source coverage, record counts, and search-index backlog to identify sync gaps and prioritize repairs.

Instructions

Return collector health, source coverage, counts and search-index backlog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full load. "Return" implies a read-only, non-destructive call, and enumerating the reported categories gives useful behavioral context in the absence of an output schema. However, it does not say whether invoking it is cheap, whether it reflects live or cached state, or whether any side effects (such as triggering a sync) occur.

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?

A single compact sentence with the verb front-loaded and no filler. Every listed item adds a distinct data category, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Absent an output schema, the description must convey what comes back, and it does so only at category level — "counts" has no stated subject (documents? messages? sources?). Combined with no annotations and no usage guidance, an agent knows the shape of the payload roughly but not the specifics or cost of calling it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims conflict with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Return") paired with four named data categories: collector health, source coverage, counts, and search-index backlog. This clearly marks it as a diagnostics/status tool rather than a record-retrieval tool like its siblings. The only soft spot is "source coverage," which could be confused with list_sources, but the overall purpose is unmistakable.

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

Usage Guidelines2/5

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

The description never states when to call this tool versus alternatives, nor any precondition such as an in-progress sync. It reads as a pure statement of output content with no routing guidance, leaving the agent to infer that this is a health-check tool.

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