Skip to main content
Glama
io.github.koten-ai/zeus-dev-helper

io.github.koten-ai/zeus-dev-helper

Official
by Koten-ai-org

sample_support_pack

Read-onlyIdempotent

Generate a read-only Markdown support paste for beer, travel, or yelp-demo sample requests, bundling the bound directory, setup steps, open checklists, and recent activity.

Instructions

Read-only paste for a beer, travel, or yelp-demo support request.

Writes nothing and calls no Zeus API. Returns one Markdown paste: sample kind, bound directory, creation log, prereqs, open checklist rows in phases 1–5, the last website_green class, local setup, recent tool names, the support-journal tail, and the last 8 wish sections. Session ids stay in support_pack_from_turn. sample=api and bare sample=yelp are refused.

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

Input Schema

NameRequiredDescriptionDefault
sampleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.8

TDQS

A3.7/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 the description only partly earns credit for restating 'writes nothing'. It does add genuinely new behavior: it makes no Zeus API calls, returns exactly one Markdown paste, redirects session ids to support_pack_from_turn, and enumerates which sample values are refused outright.

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

Conciseness3/5

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

Purpose and safety come first, which is good, but the middle sentence is a long comma-spliced inventory of returned fields that duplicates the existing output schema. That inventory is the least valuable part of the text and should have been cut or condensed.

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?

For a one-parameter, read-only tool with an output schema and full annotation coverage, the description covers purpose, side-effect profile, refusal rules, and where session ids live. The only real hole is what happens when 'sample' is left at its empty default, which an agent would need to know before calling.

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 0% and the single 'sample' parameter has no enum, so the description carries the full burden. It supplies usable value constraints (beer, travel, yelp-demo) and names two rejected inputs (sample=api, bare sample=yelp), which is meaningful guidance beyond the bare string schema. It does not say what the empty default '' produces, which is the remaining gap.

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 resource and operation: a read-only Markdown support paste covering sample kind, bound directory, checklist rows, journal tail, etc. It also implicitly distinguishes itself from support_pack_from_turn by noting that session ids live there. It loses a point because the framing is dense with project jargon ('wish sections', 'the last website_green class') and never explicitly contrasts itself with siblings like use_sample or website_green.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'for a beer, travel, or yelp-demo support request', which tells an agent the context in which to reach for it. The only explicit guidance is negative and parameter-scoped ('sample=api and bare sample=yelp are refused') rather than tool-level when-to-use/when-not-to-use or a named alternative.

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