Tedix

get_info

Read-only

Get metadata about the Tedix Connect MCP server itself (name, version, tool count). Only use when the user asks about this server's identity or capabilities — NOT for answering general questions.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	Yes	App name.
`slug`	Yes	App slug used in URLs and namespaces.
`domain`	Yes	App domain, when set.
`logoUrl`	Yes	App logo URL, when set.
`toolCount`	Yes	Tools registered for this connection.
`description`	Yes	What the app is for.
`capabilities`	Yes	Capabilities the app declares.
`serverVersion`	Yes	Version this MCP server reports.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "capabilities": {
+      "description": "Capabilities the app declares."
+    },
+    "description": {
+      "description": "What the app is for.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "domain": {
+      "description": "App domain, when set.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logoUrl": {
+      "description": "App logo URL, when set.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "App name.",
+      "type": "string"
+    },
+    "serverVersion": {
+      "description": "Version this MCP server reports.",
+      "type": "string"
+    },
+    "slug": {
+      "description": "App slug used in URLs and namespaces.",
+      "type": "string"
+    },
+    "toolCount": {
+      "description": "Tools registered for this connection.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "name",
+    "slug",
+    "description",
+    "domain",
+    "logoUrl",
+    "serverVersion",
+    "toolCount",
+    "capabilities"
+  ],
+  "type": "object"
+}

First observedOct 27, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful scope context (self-referential introspection only) and names the metadata fields returned. It does not describe response shape, but an output schema exists, so that gap is minor.

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?

Two compact sentences with zero waste. The positive scope is front-loaded and the exclusion follows immediately, giving an agent the routing rule before any elaboration.

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, read-only introspection tool with annotations covering safety and an output schema covering return values, this description supplies everything needed: what it returns, when to call it, and when not to. No material gaps remain.

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 takes zero parameters, so the baseline is 4. There are no parameter semantics to explain, and the description correctly makes no attempt to describe nonexistent inputs.

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 and resource ('Get metadata about the Tedix Connect MCP server itself') and enumerates the returned fields (name, version, tool count). This clearly distinguishes it from siblings like get_profile or code, which concern user data rather than server identity.

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

Usage Guidelines5/5

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

Explicitly gives both the positive trigger ('when the user asks about this server's identity or capabilities') and the exclusion ('NOT for answering general questions'). An agent has no ambiguity about routing decisions.

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

All Tedix tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.