rybbit-mcp

Get Rybbit Config

rybbit_get_config

Read-onlyIdempotent

Retrieve Rybbit server version and configuration details to verify deployment settings or troubleshoot compatibility issues.

Instructions

Get Rybbit server version and configuration

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`version`	No	Rybbit server version string
`mapboxToken`	No	Mapbox token (if configured)
`disableSignup`	No	Whether public signup is disabled

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.1Sep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "disableSignup": {
+      "description": "Whether public signup is disabled",
+      "type": "boolean"
+    },
+    "mapboxToken": {
+      "description": "Mapbox token (if configured)",
+      "type": "string"
+    },
+    "version": {
+      "description": "Rybbit server version string",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.5.2Apr 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that (no scope, no auth requirements, no caching notes), but the bar is low given complete annotations and an output schema.

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 front-loaded sentence with no filler; every word earns its place for a no-argument tool.

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?

An output schema exists, so the return shape need not be described, and annotations cover the safety semantics. For a zero-parameter read tool the description is sufficient, though one line on what 'configuration' entails would make it airtight.

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, so the baseline is 4. There is nothing for the description to document beyond the fact that the call is parameterless.

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?

States a specific verb (get) and resource (Rybbit server version and configuration), which is clear and distinguishable from the analytics siblings like rybbit_get_overview. It does not explicitly differentiate itself from the similarly named rybbit_update_site_config, but the read vs. update verbs make the split inferable.

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?

No explicit when-to-use or when-not-to-use guidance, but usage is strongly implied for a no-argument diagnostic tool: call it to inspect server version/config. It offers no alternatives or preconditions, leaving the agent to infer the context.

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

Deploy Server