Skip to main content
Glama

Obis

by io.github.pipeworx-io

Find Occurrences

find_occurrences
Read-onlyIdempotent

Find georeferenced marine occurrence records (latitude, longitude, date, depth, country, locality, basis of record) for a scientific name from OBIS. Optionally filter by date range. Returns the total match count plus a sample of records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records to return (default 20, max 100).
enddateNoLatest event date, YYYY-MM-DD (optional).
startdateNoEarliest event date, YYYY-MM-DD (optional).
scientificnameYesScientific name to search occurrences for, e.g. "Orcinus orca".

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by explaining that the tool returns a total match count plus a sample of records (not all results), and lists the fields included. This contextualizes the behavior beyond the 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?

The description is only two sentences: the first states the core function and output fields, the second mentions optional filtering and return format. It is front-loaded, every sentence adds value, and no unnecessary words are present.

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?

Given that there is no output schema, the description explains the return value (match count + sample of records) and lists the fields. This is sufficient for an agent to understand what to expect. However, it could clarify what 'sample' means (e.g., random or top records), but the overall completeness is high.

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%, so the baseline is 3. The description does not add new parameter-level detail beyond what the schema already provides (e.g., the optional date range filter is mentioned, but the schema already describes startdate, enddate, and limit). The description focuses on overall purpose rather than parameter semantics.

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?

The description uses a specific verb ('find') and resource ('georeferenced marine occurrence records'), lists the key fields returned, and names the data source (OBIS). This clearly distinguishes it from sibling tools like get_taxon, which deals with taxonomy rather than occurrence records.

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?

The description implies the tool is for searching occurrence data by scientific name with optional date filtering, but it does not explicitly state when to use this tool over alternatives (e.g., search_within, entity_profile) or when not to use it. There are no direct comparisons or exclusions.

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

All Obis toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools have distinct purposes and the descriptions are unusually thorough, but ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and several discovery/prediction-market tools (polymarket_edges vs polymarket_arbitrage, discover_tools vs suggest_questions) occupy overlapping territory. An agent could reasonably route to the wrong variant despite the documentation.

Naming Consistency4/5

The dominant convention is lowercase snake_case with a leading verb (ask_pipeworx, list_subscriptions, validate_claim, resolve_entity), which makes the set predictable. A few noun-first outliers like pipeworx_trending, recent_alerts, and polymarket_edge_tracker are minor deviations rather than a broken pattern.

Tool Count2/5

34 tools is well above the coherence sweet spot for an MCP server, and much of that count is made up of meta-wrappers and convenience variants around the same Pipeworx router. The broad scope explains some of the count, but the surface still feels heavy for a single named server.

Completeness3/5

The Pipeworx side is very complete: lookups, grounded verification, research, entity profiles, comparisons, prediction-market fill checks, subscriptions, and memory all have lifecycle coverage. However, the server is named Obis and only find_occurrences, get_statistics, and get_taxon serve that domain, leaving obvious marine-biodiversity operations like occurrence detail, dataset listing, and download paths missing.

Resources