Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Get Rybbit Config

rybbit_get_config
Read-onlyIdempotent

Retrieve server version and configuration details for the Rybbit Analytics MCP server to verify setup and access monitoring capabilities.

Instructions

Get Rybbit server version and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for rybbit_get_config which fetches server version and config data.
    server.registerTool(
      "rybbit_get_config",
      {
        title: "Get Rybbit Config",
        description: "Get Rybbit server version and configuration",
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
      },
      async () => {
        try {
          const [versionData, configData] = await Promise.all([
            client.get<VersionResponse>("/version"),
            client.get<ConfigResponse>("/config"),
          ]);
    
          const combined = {
            version: versionData.version,
            disableSignup: configData.disableSignup,
            mapboxToken: configData.mapboxToken,
          };
    
          return {
            content: [
              {
                type: "text" as const,
                text: truncateResponse(combined),
              },
            ],
          };
        } catch (err) {
          const message = err instanceof Error ? err.message : String(err);
          return {
            content: [{ type: "text" as const, text: `Error: ${message}` }],
            isError: true,
          };
        }
      }
    );
Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive properties. The description aligns with these (using 'Get') and specifies the scope (version + configuration). However, it adds no further behavioral context like rate limiting, caching behavior, or return structure that would help an agent interpret the response.

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?

Extremely efficient at 7 words. Front-loaded with the action verb. Zero redundancy or filler. Every word conveys essential information about the operation and its target.

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?

Adequate for a zero-parameter configuration getter with good safety annotations. While the output schema is absent, the description successfully communicates what data category will be returned (version and configuration), which is sufficient for an agent to decide whether to invoke the tool.

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?

Input schema has zero parameters. Per scoring rules, 0 parameters establishes a baseline of 4. No parameter semantics are needed or provided, which is appropriate for this simple metadata retrieval tool.

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?

Clear verb ('Get') and resource ('Rybbit server version and configuration'). It implicitly distinguishes from sibling analytics tools (e.g., get_metric, get_events) by specifying server-level metadata, though it could explicitly clarify this is global/instance configuration vs. site-specific configuration (rybbit_update_site_config).

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 guidance, but the implied usage is clear: invoke this to retrieve server diagnostics or verify version compatibility. Given zero parameters and straightforward purpose, this is acceptable minimal guidance, though explicit context (e.g., 'Use for health checks') would improve it.

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/nks-hub/rybbit-mcp'

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