Skip to main content
Glama

get_sync_cadence

Read-onlyIdempotent

How often a connected source syncs, per data type (costs, events, usage): the effective rate, the default, and the choices with whether this plan may take each (faster rates need a paid plan; fast_sync_enabled says whether it does). Mirrors GET /api/accounts/:accountId/sync-cadence/:sourceId. Change a rate with set_sync_cadence.

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": {
      "source_id": "<source_id>"
    },
    "name": "get_sync_cadence"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesThe connected source, for example "gcp" or "github"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds domain behavior the annotations cannot: that returned choices carry plan entitlement (faster rates need a paid plan) and that fast_sync_enabled signals eligibility — meaningful context for interpreting the result.

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 what is returned, then the plan/entitlement caveat, then the alternative tool. Dense but every clause carries information an agent needs; no filler.

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

Completeness4/5

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

No output schema exists, and the description compensates by naming the returned fields (effective rate, default, choices, fast_sync_enabled) plus the underlying endpoint, which is enough to form expectations. Minor gap: it does not describe nesting or per-data-type structure of the response.

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% and the single source_id parameter is already documented with examples ('gcp', 'github'). The description only echoes that identifier via the REST path and adds no new input semantics such as accepted aliases or lookup rules; 'costs, events, usage' describes output, not input. Baseline 3 applies.

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?

States a specific resource and read operation ('How often a connected source syncs, per data type') and enumerates the returned facets (effective rate, default, choices). It also names the mutation counterpart set_sync_cadence, so an agent can tell read from write immediately.

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 closing sentence explicitly routes change operations to set_sync_cadence, which is real when-to-use-else guidance. It lacks an explicit when-not or prerequisite statement (e.g., that the source must be connected), but the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources