Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_cluster

Monitor cluster health by checking staleness, scope drift, vault status, and receive actionable recommendations.

Instructions

Aggregate maintenance view: staleness + scope drift + vault health + recommendations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_slug": "<cluster_slug>"
    },
    "name": "sync_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_slugYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a 'view', implying read-only behavior, but does not explicitly confirm idempotency, side effects, or whether it requires authentication. The description adds minimal behavioral context beyond the name.

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

Conciseness4/5

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

The description is a single sentence with no extraneous words. It is front-loaded with the tool's purpose and lists key content areas. However, it could be slightly more structured (e.g., listing what the output includes) without adding length.

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

Completeness2/5

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

Given the output schema exists, the description could omit return details, but it does not mention the tool's scope (e.g., whether it covers all clusters or suggests actions). With only one parameter and no nested objects, the description is still too sparse to fully guide correct invocation.

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

Parameters1/5

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

The only parameter, 'cluster_slug', lacks any description in the schema (0% coverage) and the tool description provides no explanation of what constitutes a valid slug, its purpose, or formatting. The agent has no guidance on constructing this parameter correctly.

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

Purpose3/5

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

The description 'Aggregate maintenance view' suggests a read-only overview but lacks an explicit verb (e.g., 'get', 'list'). It lists covered areas (staleness, scope drift, etc.) but does not clearly differentiate from sibling tools like 'read_crystal' or 'show_cluster' that may provide similar views.

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?

No guidance on when to use this tool versus alternatives. The description does not specify prerequisites, when to invoke it, or when not to. Given the large set of sibling tools, this omission reduces usability.

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

Deploy Server

Other Tools