Skip to main content
Glama
Sign In
Rowbase

Rowbase

by djstreet11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Guide

guide
Read-onlyIdempotent

Learn Rowbase's recommended workflow, safety rules, TOON output format, and SQL dialect notes before using any other tool. Read once per session; no connection needed.

Instructions

Read this first, once per session: the Rowbase knowledge base — recommended workflow, safety rules (read-only model, one statement per call), the TOON output format and SQL dialect notes. Use it before any other tool; it needs no connection. Returns a markdown document.

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": "guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds genuine operational context beyond that: the document is a markdown return, requires no connection, and it previews the platform's read-only model and one-statement-per-call rule. Return format and connection requirement are the key value-adds.

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?

One dense sentence with the imperative 'Read this first' front-loaded, followed by a compact parenthetical inventory. Every clause carries information; no filler.

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?

With no output schema present, the description compensates by stating the return type ('Returns a markdown document'), and it discloses the guide's contents and the no-connection prerequisite. Nothing an agent needs in order to call it correctly is missing.

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?

Zero parameters, so there is nothing to disambiguate; baseline is 4. The description correctly signals this by noting it 'needs no connection', reinforcing that the call is argument-free.

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 action and resource: read the Rowbase knowledge base document, with an enumerated inventory of what it contains (workflow, safety rules, TOON format, SQL dialect notes). This is unmistakably distinct from every sibling, which are all data-access 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?

Explicit timing is given twice ('Read this first', 'Use it before any other tool') plus a frequency constraint ('once per session') and a prerequisite note ('needs no connection'). An agent knows exactly when to call it and that all other tools follow it.

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