Skip to main content
Glama
lundgrenalex

MCP FishBase Server

by lundgrenalex

list_tables

Discover available FishBase tables to access marine biology data including species information, ecological data, and distribution records.

Instructions

List all available FishBase tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the list_tables tool, returning a hardcoded array of available FishBase table names.
    async listTables(): Promise<string[]> {
      return [
        'species',
        'ecology',
        'occurrence',
        'morphdat',
        'comnames',
        'spawning',
        'diet',
        'popgrowth',
        'stocks',
        'synonyms',
        'taxa',
        'estimate',
        'ecosystem',
      ];
    }
  • MCP tool dispatch handler for list_tables, which invokes fishbaseAPI.listTables() and formats the response as JSON text.
    case "list_tables":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await fishbaseAPI.listTables(),
              null,
              2
            ),
          },
        ],
      };
  • Tool schema definition including name, description, and empty input schema for list_tables.
    {
      name: "list_tables",
      description: "List all available FishBase tables",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:27-148 (registration)
    Registration of all tools including list_tables in the MCP server's listTools request handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "get_species",
            description: "Get species information from FishBase",
            inputSchema: {
              type: "object",
              properties: {
                species_name: {
                  type: "string",
                  description: "Scientific name of the species (e.g., 'Salmo trutta')",
                },
                fields: {
                  type: "array",
                  items: { type: "string" },
                  description: "Optional list of specific fields to return",
                },
              },
              required: ["species_name"],
            },
          },
          {
            name: "search_species",
            description: "Search for species by common name or partial scientific name",
            inputSchema: {
              type: "object",
              properties: {
                query: {
                  type: "string",
                  description: "Search term (common name or partial scientific name)",
                },
                limit: {
                  type: "number",
                  description: "Maximum number of results to return (default: 20)",
                  default: 20,
                },
              },
              required: ["query"],
            },
          },
          {
            name: "get_ecology",
            description: "Get ecological information for a species",
            inputSchema: {
              type: "object",
              properties: {
                species_name: {
                  type: "string",
                  description: "Scientific name of the species",
                },
              },
              required: ["species_name"],
            },
          },
          {
            name: "get_distribution",
            description: "Get distribution/occurrence information for a species",
            inputSchema: {
              type: "object",
              properties: {
                species_name: {
                  type: "string",
                  description: "Scientific name of the species",
                },
              },
              required: ["species_name"],
            },
          },
          {
            name: "get_morphology",
            description: "Get morphological and physiological data for a species",
            inputSchema: {
              type: "object",
              properties: {
                species_name: {
                  type: "string",
                  description: "Scientific name of the species",
                },
              },
              required: ["species_name"],
            },
          },
          {
            name: "validate_species_name",
            description: "Validate and correct species scientific names",
            inputSchema: {
              type: "object",
              properties: {
                species_name: {
                  type: "string",
                  description: "Scientific name to validate",
                },
              },
              required: ["species_name"],
            },
          },
          {
            name: "common_to_scientific",
            description: "Convert common name to scientific name",
            inputSchema: {
              type: "object",
              properties: {
                common_name: {
                  type: "string",
                  description: "Common name of the fish",
                },
              },
              required: ["common_name"],
            },
          },
          {
            name: "list_tables",
            description: "List all available FishBase tables",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
        ],
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but lacks behavioral details such as whether this is a read-only operation, if it requires authentication, what the output format looks like (e.g., list of table names), or any rate limits. This leaves significant gaps for an agent to understand how to handle the tool effectively.

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 a single, clear sentence with zero waste—it directly states the tool's purpose without fluff. It is front-loaded and appropriately sized for a simple, parameterless tool, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks context on output format or integration with sibling tools. For a metadata-listing tool, this is a basic but functional description that could be more complete by addressing its role in the broader toolset.

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 has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately avoids redundant parameter info, earning a baseline score of 4 for not adding unnecessary details beyond the empty 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?

The description clearly states the verb ('List') and resource ('all available FishBase tables'), making the purpose unambiguous. However, it does not differentiate from sibling tools, which are all about species data rather than table metadata, so it misses an opportunity to clarify its distinct role in the toolset.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. Given the sibling tools focus on species-related queries (e.g., get_species, search_species), it's unclear if this tool is for metadata exploration or a prerequisite for other operations, leaving usage context implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lundgrenalex/mcp-fishbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server