Skip to main content
Glama
Sign In
abba-mcp

abba-mcp

Official
by unige-biochem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

fiji_module_search

Read-only

Search Fiji and SciJava modules by words in title, menu path, description, or class; every query word must match, helping locate commands or scripts before coding.

Instructions

Find SciJava commands and scripts whose title, menu path, description or class contain all the words of the query. Every Fiji command and plugin is a module: search here before writing code. Every ABBA action is a command: search here, or grep the command docs.

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

Input Schema

NameRequiredDescriptionDefault
queryYeswords that must all appear, e.g. 'gaussian blur'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read operation. The description adds the semantics of the search (matching all words across multiple fields), which is useful but doesn't go beyond what annotations and schema imply. No return format or pagination details are given.

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?

Three sentences, front-loaded with the core purpose and matching semantics, followed by usage guidance. Efficient, with no obvious filler, though the second and third sentences are somewhat repetitive in their 'search here' phrasing.

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?

For a single-parameter read-only search tool with full schema coverage and annotations, the description covers purpose, matching behavior, and when to use it. It lacks details on result ordering or limits, but those are minor given the tool's simplicity and the absence of an output schema.

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 100%, and the schema description already explains the query parameter with an example. The description restates the matching logic ('contain all the words of the query') but adds no new syntax or format details beyond the schema.

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 (find/search) and resource (SciJava commands and scripts), and names the searchable fields (title, menu path, description, class). This is concrete and distinguishes it from siblings like fiji_module_describe and fiji_module_run, though it doesn't explicitly contrast with those tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'search here before writing code' and 'search here, or grep the command docs', giving clear when-to-use guidance with alternatives. The imperative phrasing directs the agent to use this as a discovery step.

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

Deploy Server

Other Tools