Skip to main content
Glama

fishwatch_species

Returns an unavailable error because NOAA retired the FishWatch species API. Indicates that species data cannot be retrieved.

Instructions

Retired upstream: NOAA shut the FishWatch species API. Answers with a plain unavailable error and makes no request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fishwatch_species"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations to lean on, the description carries the full behavioral burden and does so completely: it discloses that no upstream request is made and that the caller receives a plain unavailable error. Those are exactly the two facts an agent needs to avoid wasting a call or misinterpreting a failure as transient.

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?

A single sentence that front-loads the decisive fact ('Retired upstream') before the behavioral consequence. Nothing is padded and nothing an agent needs is buried.

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 zero-parameter, no-output-schema, retired endpoint, the description covers status, failure mode, and absence of side effects—everything required. No permissions, pagination, or return-shape details are relevant when no request is made.

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?

The tool takes zero parameters and the description correctly makes no parameter claims, matching the empty schema with additionalProperties false. Baseline for a 0-param tool is 4; there is nothing further to document.

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 and lifecycle status: the FishWatch species API endpoint, retired upstream by NOAA. An agent immediately knows what the tool nominally did and that it is dead, distinguishing it plainly from the still-live fishwatch_species_detail sibling.

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?

The word 'Retired' plus 'answers with a plain unavailable error and makes no request' is an unambiguous signal not to call it for data, which functions as an implicit when-not-to-use rule. It does not name a replacement (e.g. fishwatch_species_detail or gbif_search_species), so it stops short of explicit routing to an alternative.

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