Skip to main content
Glama
Sign In
Rockfish MCP Server

Rockfish MCP Server

Official
by Rockfish-Data
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_database

Retrieve a specific database by ID from the Rockfish AI platform to manage datasets and support synthetic data generation or ML workflows.

Instructions

Get a specific database by ID

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": {
      "id": "<id>"
    },
    "name": "get_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDatabase ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
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 behavioral burden. 'Get' implies a read, but there is no statement about permissions, error behavior, or return characteristics. This is a minimal read operation, but the description does not actively disclose behavioral traits beyond the verb.

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 front-loaded sentence with no wasted words. It is appropriately sized for a simple lookup tool and makes its point immediately.

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?

For a simple one-parameter lookup with no output schema and no annotations, the description is minimally sufficient to select and invoke the tool. However, it omits usage context and any indication of what is returned, leaving some gaps that a fuller description could address.

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% for the single 'id' parameter, so the schema already documents that 'Database ID' is expected. The description's 'by ID' adds no meaning beyond the schema, which matches the baseline of 3 when the schema does the heavy lifting.

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 gives a specific verb ('Get') and resource ('database') and scopes it to a single record via 'by ID', which distinguishes it from list_databases and the create/update/delete siblings. It stops short of explicitly naming an alternative or sibling, so a 4 is appropriate.

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 only usage cue is the implicit 'by ID' condition, which tells the agent that an ID is required but does not explain when to choose this tool over list_databases or get_dataset. No alternatives or exclusions are mentioned.

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