TimeBase MCP

Official

Overview Schema Source Related Servers Discussions Admin

list_qql_functions

Read-only

List QQL function signatures supported by TimeBase, with optional filters for category or function ID to verify function availability.

Instructions

List QQL function signatures supported by the connected TimeBase server

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	Function category to return	all
`function_id`	No	Optional exact QQL function id to return, e.g. ABS or SMA. Letters, digits and underscores only. When provided, TimeBase filters overloads server-side.
`instance_key`	No	TB instance key. Required when multiple TimeBase instances are configured.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`stateful`	No
`stateless`	No
`function_count`	No
`overload_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.2Aug 5, 2026

changedInput schema / properties / function_id / description

Previous value: -"Optional exact QQL function id to return, e.g. ABS or SMA. When provided, TimeBase filters overloads server-side."New value: +"Optional exact QQL function id to return, e.g. ABS or SMA. Letters, digits and underscores only. When provided, TimeBase filters overloads server-side."

First observedv0.2.1Jul 31, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and openWorldHint, so the description's addition of 'supported by the connected TimeBase server' adds a meaningful caveat about dynamic results. However, it does not detail other behavioral aspects like filtering behavior or output structure, which are left to annotations and 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, grammatically clear sentence that is front-loaded with the action and resource. No filler or redundancy.

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?

The tool has an output schema and all parameters are documented in the schema. The description sufficiently defines the tool's core purpose; however, it omits context about filtering options, but the schema covers those. Overall it is complete for a read-only list operation.

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% (each parameter has a description). The tool description does not add any parameter-specific value beyond the schema, so baseline of 3 is appropriate.

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 states a specific verb ('List') and resource ('QQL function signatures') with a clear scope ('supported by the connected TimeBase server'). It clearly distinguishes from sibling tools like list_streams or execute_query.

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?

The description implies the tool is used when you need to know available QQL functions, but it does not explicitly state when to use it versus alternatives or mention any exclusions. The context is clear but not directly instructional.

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

Deploy Server