Skip to main content
Glama

generate_refresh_schedules

Idempotent

Creates cron schedules for data concepts based on each concept's indicator_defs.frequency, enabling automated refresh planning without manual cron setup.

Instructions

Generate cron schedules for concepts from their indicator_defs.frequency.

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": "generate_refresh_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already disclose that this is a non-read-only, non-destructive, idempotent operation, so the agent knows it writes something safely re-runnable. The description adds only where the input data comes from (indicator_defs.frequency) and says nothing about what is created, where schedules are stored, whether existing schedules are replaced or appended, or what permissions are needed.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the missing behavioral and workflow information rather than a virtue in itself.

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?

Complexity is low (zero parameters) and an output schema exists, so return values need no explanation here. However, for a mutation tool that implicitly operates over all concepts, the definition omits the facts an agent most needs: which concepts are in scope, what happens to previously generated schedules, and where the result is persisted.

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 no parameters, so there is nothing for the description to disambiguate at the argument level. The baseline for a zero-parameter tool is 4, and the sentence does not mislead about inputs; the scoping shown in the description is implicit, not parameterized.

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?

The description names a specific verb ('Generate') and resource ('cron schedules') and states the derivation source ('concepts from their indicator_defs.frequency'), so the agent knows this produces schedule entries from concept metadata. It does not explicitly contrast with the sibling 'list_schedules', but the purpose is unambiguous from the verb and object.

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?

There is no guidance on when to invoke this versus 'list_schedules' or the import/add tools, no statement of prerequisites (e.g., that concepts and indicator_defs must already be loaded), and no indication of whether it must be run before listing schedules. The agent must infer the workflow entirely.

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