Skip to main content
Glama
Sign In
Velixar MCP Server

Velixar MCP Server

Official
by VelixarAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

velixar_list_sources

Retrieve a list of connected data sources for your customer account, with optional filters by source type and connection status.

Instructions

List all connected data sources for the current customer. Supports filtering by type and status.

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by source type (e.g., "relational", "saas", "file")
statusNoFilter by connection status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It fails to disclose whether the operation is read-only, requires authentication, returns paginated results, or has side effects. The phrase 'list all' suggests a safe read, but this is unconfirmed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the main action and follow with filtering support. No wasted words, though the second sentence could be more specific about which parameters apply.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description covers the basics but omits potential concerns like pagination, result ordering, or error handling. It is adequate but not thorough.

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 coverage is 100% and both parameters have clear descriptions in the schema. The description merely restates the filtering capability without adding new details, meeting the baseline expectation.

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 clearly states the tool's action ('list'), the resource ('connected data sources'), and scope ('for the current customer'). It also mentions filtering options, which distinguishes it from generic list tools like 'velixar_list'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs. alternatives like 'velixar_discover_data' or 'velixar_query_source'. The description implies its purpose but does not set boundaries or prerequisites.

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