Skip to main content
Glama
crunchtools

mcp-metsuke-crunchtools

Official
by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

upsert_definition_tool

Create or update a report definition with a gather prompt, owner agent, and cron schedule so Metsuke fires cited reports automatically.

Instructions

Create or update a report definition.

The owner_agent field makes the gatherer identity data, not code, so gathering can be re-homed to another agent without a rebuild. The schedule is a live cron expression: Metsuke's built-in scheduler fires the report when it comes due, in the given timezone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique report name (e.g. "core-platform-status")
scheduleNoCron expression for when to fire (e.g. "0 6 * * 5"); None = manual only
timezoneNoIANA timezone the schedule runs in (default: "UTC")UTC
owner_agentNoWhich agent gathers this report (default: "kagetora")kagetora
gather_promptYesThe instruction the gatherer runs to collect findings
source_configNoWhich sources to sweep, as a JSON object

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • changedInput schema / properties / schedule / description
      Previous value: -"Descriptive cron/time metadata (the actual firing is external)"New value: +"Cron expression for when to fire (e.g. \"0 6 * * 5\"); None = manual only"
    • addedInput schema / properties / timezone
      Added value: +{
+  "default": "UTC",
+  "description": "IANA timezone the schedule runs in (default: \"UTC\")",
+  "type": "string"
+}
  2. First observedv0.2.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 must carry the behavioral burden. It usefully discloses upsert semantics, that owner_agent makes identity data rather than code (re-homing without a rebuild), and that schedule is a live cron fired by the built-in scheduler. It omits update-overwrite behavior, permission requirements, and side effects, so it adds context but not a full behavioral picture.

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?

The core action is front-loaded in the first sentence, followed by two tight sentences that each explain a distinct field behavior. No filler or repetition.

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?

An output schema exists, so return values need no explanation. For a six-parameter upsert mutation with no annotations, the description covers the two most conceptually important fields but leaves source_config, gather_prompt, and the update-vs-create behavioral distinction unaddressed, making it adequate but incomplete.

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?

Schema coverage is already 100%, but the description adds genuine meaning beyond it: owner_agent carries the re-homing rationale and schedule is framed as a live cron fired by Metsuke's scheduler. This enriches at least two parameters above the schema baseline, though source_config and gather_prompt remain unaddressed.

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?

States a specific verb pair (create or update) and resource (report definition), which is clear. However it does not differentiate from siblings like list_reports_tool, trigger_report_tool, or delete_output_tool, so the agent gets a precise action but no routing contrast.

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 text explains field semantics rather than when to invoke this tool versus alternatives. There is no when-to-use, when-not-to-use, or sibling routing guidance (e.g., trigger_report_tool for firing an existing report), leaving the agent to infer selection.

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