Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_version

Retrieve the Datris server version and the active tap budget limits before sizing large sources, so you can compare estimates against this install's real values instead of documented defaults.

Instructions

Get the Datris server version and the tap budgets in force on this install: pipelineMaxPayloadMB (MB, 0 = unlimited), tapScriptTimeoutSeconds and tapRunTimeoutSeconds, each with a ...Source field (env, deprecated-alias, derived or default). Cheap to call: call it before sizing a large source and compare the estimates with these values, not with the documented defaults (the budget fields are absent on a server older than this feature; then the documented defaults apply). It also returns environmentLabel when the operator set DATRIS_ENV on the server (absent otherwise).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations and no output schema, the description carries the full disclosure burden and does so: it names every returned field, flags that budget fields are absent on older servers and that documented defaults then apply, and notes environmentLabel is present only when DATRIS_ENV was set. It also discloses cost ('cheap to call'), which is exactly the kind of behavioral trait an agent needs before deciding to invoke.

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?

Front-loaded with the purpose, then progressively narrower detail on fields and version-gating; no filler sentences. The parenthetical clauses make the second sentence dense on first read, but each clause (units, 0 = unlimited, source origins, older-server fallback) earns its place by preventing a misread.

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

Completeness5/5

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

For a zero-parameter, no-annotation, no-output-schema tool, the description supplies everything needed: what comes back, what may be missing and why, what fallback applies, and how to use the values. Nothing an agent needs in order to call it correctly or interpret the response is absent.

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?

Zero parameters, so there is nothing for the description to disambiguate; it instead spends its words on the semantic meaning of the returned budget fields (units, 0 = unlimited, the ...Source provenance enum). That is useful added meaning, but it is return-value semantics rather than parameter semantics, so it sits at the no-parameter baseline.

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?

States a specific verb+resource: 'Get the Datris server version and the tap budgets in force on this install', then enumerates the exact fields returned so the agent knows the payload shape. This clearly separates it from the version-related siblings (get_pipeline_version, get_tap_version), which are about artifacts rather than the server install.

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

Usage Guidelines4/5

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

Gives an explicit trigger and a concrete instruction: 'call it before sizing a large source and compare the estimates with these values, not with the documented defaults'. That is stronger than a generic context hint, though it does not state when not to call it (the 'cheap to call' note implies there is little downside, which covers that implicitly rather than explicitly).

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