Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

get_workflows

Read-only

Retrieve step-by-step tool sequences for common spreadsheet tasks such as merging workbooks, building reports, or cleaning data. Call with a task name to see its recipe and notes.

Instructions

Recommended tool sequences for common multi-step spreadsheet tasks, each step naming the tool, the rationale, and the pack it lives in (lite is always on; enable_tools loads the rest). Call with no task to list the available tasks (merge-workbooks, report-build, data-cleanup, formatting-audit-and-fix, safe-edit-of-rich-workbook, migrate-from-incumbent); call with task='' for that task's step-by-step recipe and notes. Steps naming COM-tier tools that have not shipped yet are marked forthcoming rather than pretended present. Pure guidance: reads nothing, changes nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description explicitly states 'Pure guidance: reads nothing, changes nothing', which fully communicates the tool's side-effect profile. It also discloses that COM-tier tools that have not shipped are marked as forthcoming rather than pretended present, adding honesty about content reliability.

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 description is dense but every sentence earns its place: purpose, invocation modes, task values, pack behavior, status honesty, and safety. The structure front-loads the core purpose and then clearly separates list mode from recipe mode, making it easy to parse.

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

Completeness5/5

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

For a read-only guidance tool with one optional parameter and no output schema, the description fully covers what the agent receives in each mode, which task names are valid, and that the tool has no side effects. Nothing essential is missing for correct selection and invocation.

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

Parameters5/5

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

The input schema has no parameter descriptions, but the description fully compensates by explaining the null/default behavior, listing valid task names, and specifying what happens with each invocation. An agent can correctly pass the task parameter without needing extra schema documentation.

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?

The description clearly states that this tool returns recommended tool sequences for common multi-step spreadsheet tasks, and it distinguishes between listing available tasks and retrieving a step-by-step recipe. It also separates this tool from sibling spreadsheet operations by labeling it 'Pure guidance', so an agent can understand exactly what it is without inspecting other definitions.

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 description gives explicit invocation patterns: call with no task to list available tasks, or call with task='<name>' for a recipe. It also enumerates valid task names, which strongly guides an agent on when and how to use the tool. It does not explicitly state when not to use it, but the call patterns and purpose make the intended usage clear.

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

Install Server

Other Tools