Faldaro

create_sequence

Create a reference-number sequence, e.g. prefix "CLM-", padding 5 → CLM-00001. Its slug (derived from the name) is what a REFERENCE_NUMBER logic effect references via generator. Allocation semantics the user may ask about: a submission draws its number once, when it is saved, and keeps it forever — editing never renumbers, and evaluation previews never consume a number. Check list_sequences first rather than creating a near-duplicate. Requires sequence:write.

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

Input Schema

Name	Required	Description
`name`	Yes	Sequence name, e.g. "Claim numbers"; the slug derives from it.
`prefix`	No	Text before the number, e.g. "CLM-".
`suffix`	No	Text after the number.
`padding`	No	Zero-padding width, e.g. 5 → 00001.
`startAt`	No	First value to allocate (default 1).
`description`	No	Optional description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations by explaining allocation semantics: numbers are drawn once when saved, never renumbered on edit, and evaluation previews never consume a number. Also discloses the slug-derivation behavior and the required sequence:write permission. No contradiction with annotations.

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?

Every sentence earns its place: an illustrative example, the critical slug/generator relationship, allocation semantics, duplicate-check guidance, and permission. The content is front-loaded with the core purpose before the finer behavioral details.

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 creation tool with no output schema, the description covers purpose, behavioral quirks, an important pre-check, and required permission. The only minor omission is an explicit return-value description, but the operational guidance is otherwise complete.

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 100%, so the baseline is 3. The description adds meaningful context beyond the schema by clarifying that the slug derived from name is what REFERENCE_NUMBER logic references via generator, and by giving a working prefix/padding example. This makes the name parameter's role significantly clearer.

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?

States a specific verb+resource: 'Create a reference-number sequence' with a concrete example (CLM-00001). It clearly differentiates from the broad create_* siblings by focusing on sequence creation and the slug/generator mechanism.

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?

Explicitly directs agents to check list_sequences before creating a near-duplicate, which is a clear pre-condition and when-not-to-use signal. It does not explicitly mention update_sequence as the alternative for modifying an existing sequence, so the guidance is strong but not fully exhaustive.

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

All Faldaro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?