LLM Bus

seed_sequence

Initialize a sequence counter at a given offset with an optional prefix and zero-padding, ensuring the counter never decreases.

Instructions

Initialize/seed a sequence at an existing offset and set its format (prefix + zero-pad), e.g. seed 'adr' at 102 with prefix 'R'. Never rewinds a counter.

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": {
      "sequence": "<sequence>",
      "current": "<current>"
    },
    "name": "seed_sequence"
  }
}

Input Schema

Name	Required	Description	Default
`sequence`	Yes
`current`	Yes
`prefix`	No
`pad`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only discloses 'Never rewinds a counter', omitting idempotency, error conditions, side effects, or whether it creates missing sequences.

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?

Single sentence plus example, no unnecessary words. Extremely concise while conveying core purpose.

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?

Given no output schema and 0% schema coverage, the description is too minimal. It lacks return value, error handling, and complete parameter details, making it insufficient for an agent to reliably invoke the tool.

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

Parameters3/5

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

Schema coverage is 0%, so description must compensate. It explains 'sequence', 'current' (offset), 'prefix' via example, but does not clarify 'pad' meaning (zero-pad length) or validate format constraints.

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 clearly states the tool initializes/seeds a sequence with a format, using specific verb and resource. It distinguishes from siblings like list_sequences by focusing on seeding rather than listing, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives. The only behavioral note is 'Never rewinds a counter', but lacks context on prerequisites (e.g., does the sequence need to exist?) or when not to use.

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