Skip to main content
Glama
time-direction
by GEsoFo

build_election_request

Generate 1–7 day joint timing materials and offline HTML for model adjudication, preserving cross-month windows.

Instructions

生成1至7日的联合择时判断材料及离线HTML;逐批读材料后由模型裁决。跨月不会漏掉窗口。

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": {
      "start": "<start>"
    },
    "name": "build_election_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
startYes
purposeNo
mountainNo
observerNo
rolloverNo
participantsNo
qimen_methodNo拆补法 / 置闰法(九日含符首、接气借下元)chaibu
noble_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this writes locally without external side effects. The description adds that an offline HTML file is produced and that materials are consumed batch-by-batch, but it never says where the HTML is written or whether prior outputs are overwritten.

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?

Two tight clauses with the output artifact front-loaded and the workflow note second. No filler, though the second sentence is dense given the semantic load it carries.

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

Completeness2/5

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

For a tool with 9 parameters, a nested observer object, a participants array, 4 enums, and no output schema, this description is far too thin. An agent cannot infer what mountain, noble_profile, qimen_method alternatives, or participant branch values mean, nor what the returned materials look like.

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

Parameters2/5

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

Schema description coverage is only 11% across 9 parameters, so the description carries the burden and largely fails. "1至7日" maps to the days bound and "跨月" hints at rollover/month-boundary handling, but observer, participants, mountain, purpose, start, and noble_profile receive no explanation of format or effect.

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 gives a specific verb+resource: generate 1-7 days of joint electional-timing judgment materials plus an offline HTML artifact. It is clear what the tool produces, but it never distinguishes itself from siblings like render_election_calendar or preview_election_calendar, which plausibly produce overlapping HTML output.

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?

"逐批读材料后由模型裁决" implies a downstream workflow (read the materials in batches, then let the model adjudicate) and "跨月不会漏掉窗口" hints at when this tool is preferable. However, no explicit when-to-use vs. when-not guidance and no named alternatives among the seven siblings are given.

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