Skip to main content
Glama

jean — Molecular Biology & Genomics

by io.github.genmnz
OverviewDiscussionsAdmin

filter_items

Read-only

Keep only the rows of a table-shaped output that meet a condition — the bands above a size, the guides over a score, the assays under a penalty. Emits the kept rows plus how many were dropped, so a downstream gate can act on the count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoupper bound, inclusive. Only applies when operator is between.
minNolower bound, inclusive. Only applies when operator is between.
setNothe values the field must be one of (or none of). Only applies when operator is in or not_in.
textNothe text a field must contain. Only applies when operator is contains.
fieldNowhich field of each row to test (e.g. `size`, `score`, `length`). Leave empty to test the row itself when it is a plain number.
itemsYesthe rows to filter — wire a json/list output (bands, guides, assays, amplicons).
valueNothe value to compare against. Only applies when operator is == or != or > or >= or < or <=.
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
operatorNohow to compare. Values: == (equals), != (does not equal), > (greater than), >= (at least), < (less than), <= (at most), between (between (inclusive)), in (is one of), not_in (is none of), contains (contains text), is_true (is true), not_empty (is not empty).>=

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYeshow many rows were kept — wire this into check_value to gate on it
itemsYesthe rows that met the condition
droppedYeshow many rows were removed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it emits the kept rows plus a count of dropped rows, which signals the return shape and the downstream gating intent.

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?

Two tight sentences that lead with the core operation and follow with the output/gating behavior. No filler, no restatement of the tool name, and the most important information is front-loaded.

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?

An output schema exists and the schema documents all 10 parameters, so return values and argument semantics need not be re-explained. The description covers purpose and output intent adequately for a filter tool, leaving only sibling routing unaddressed.

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 description coverage is 100%, and every operator (between, in, contains, comparisons) and its bound parameters are documented in the schema itself. The description offers only the generic word 'condition' and adds no syntax, defaults, or field-selection guidance beyond it, so the baseline of 3 applies.

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 verb (keep/filter) and resource (rows of a table-shaped output) with concrete domain examples (bands above a size, guides over a score, assays under a penalty). This is far more specific than its neighbors, though it never names an alternative sibling like summarize_rows or check_rows to draw the boundary explicitly.

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 only implied through the mention that a downstream gate can act on the dropped count, which hints at conditional downstream routing. There is no explicit when-to-use or when-not-to-use statement versus related tools such as check_rows, summarize_rows, or pick_first.

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

All jean — Molecular Biology & Genomics toolsInspect
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