Convert fuzzy or relaxed search strings into strict Seq filter syntax, making queries like 'error' or 'user==alice' work as valid log filters.
Convert a fuzzy or relaxed user search string into strict Seq filter syntax (e.g. converts 'error' or 'user==alice' into strict expressions).
| Name | Required | Description | Default |
|---|---|---|---|
| workspace | No | Optional workspace identifier. | |
| fuzzyFilter | Yes | The relaxed or fuzzy filter expression to convert. |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not say whether the tool errors on already-strict input, whether conversion is idempotent, whether the workspace parameter scopes or authorizes the call, or what the response contains (e.g. the converted string). For a transformation tool with zero annotation coverage, this is a notable gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with an embedded parenthetical example. It is efficient with no wasted words, though the example could have been separated for readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The purpose and input format are adequately conveyed, but with no annotations and no output schema, the description leaves the return value, error behavior, and workspace semantics unstated. Minimum viable for a simple two-parameter conversion tool, but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters are already documented in the schema, establishing a baseline of 3. The description adds a little meaning by showing example fuzzy inputs, but does not explain the optional workspace parameter or output semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (convert) and resource (fuzzy/relaxed user search string) with the target format (strict Seq filter syntax) and gives two concrete input examples. It is clear but does not differentiate itself from siblings like seq_search or seq_query, which may also accept filters.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus seq_search or seq_query, nor any mention of prerequisites or when conversion is unnecessary. The examples hint at the input shape, but no alternatives or exclusions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.