TimeBase MCP

Official

Overview Schema Source Related Servers Discussions Admin

get_server_configuration

Read-only

Retrieve the current MCP server runtime configuration. Use it to inspect settings, noting that some fields remain undefined or use defaults until the first connection is established.

Instructions

Get the MCP server runtime configuration, some TB server configuration fields may be undefined or have default value until the first connection is established.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`version`	Yes
`principal`	No
`transport`	Yes
`inbound_auth_mode`	No	none
`oauth_redirect_uri`	No
`timebase_instances`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.4Sep 24, 2026

addedOutput schema / $defs / TimeBaseServerConfiguration / properties / webadmin_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Webadmin Url"
+}

Changed1 schema field changedv0.2.2Aug 5, 2026
- addedOutput schema / $defs / TimeBaseServerConfiguration / properties / read_only
```
Added value: +{
+  "default": false,
+  "title": "Read Only",
+  "type": "boolean"
+}
```
First observedv0.2.1Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The readOnlyHint annotation already marks the operation as safe, and the description adds meaningful behavioral context by warning that some TB server configuration fields may be undefined or have default values until the first connection. This helps the agent avoid misinterpreting returned configuration.

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 sentence front-loads the primary purpose and immediately follows with a concise, relevant caveat. There is no filler, redundancy, or repeated annotation content.

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?

With no parameters, a read-only annotation, and an output schema present, the description is nearly complete. The only minor gap is that the abbreviation 'TB' is not expanded, which could cause slight ambiguity for agents unfamiliar with the context.

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 zero parameters, so the schema requires no additional explanation. The description's caveat concerns output field behavior rather than arguments, which is acceptable; the zero-parameter baseline of 4 applies.

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?

The description uses the specific verb 'Get' and precise resource 'MCP server runtime configuration', which clearly sets it apart from sibling tools focused on streams, timebase instances, or queries. The added caveat about undefined/default fields further clarifies the scope.

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 alternative routing is stated, but the resource name makes the purpose obvious. Usage context is implied rather than spelled out, which is adequate but not exemplary.

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

Deploy Server