Skip to main content
Glama
Sign In
thatmgmt-mcp

thatmgmt-mcp

by Thingscorp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmgmt_health

Check whether the ThatMgmt API is reachable to verify setup without an API key. Use this to confirm your connection is working.

Instructions

Check that the ThatMgmt API is reachable. No API key needed. Use it to verify setup.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It does disclose that no API key is needed and that the tool is a reachability check, but it does not describe the expected response format, error behavior, or what 'reachable' means operationally.

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?

The description is three short sentences with no filler. The main action is front-loaded, and each sentence adds distinct value: what it does, the auth requirement, and when to use it.

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?

For a zero-parameter health-check tool, the description covers purpose, setup verification, and auth. A minor gap is the lack of any mention of return values or success/failure indicators, especially since there is no output schema to clarify those details.

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 baseline is 4. The description adds the relevant context that no API key is needed, which is effectively the only 'input' consideration for this tool. Nothing else is required.

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 ('Check') and resource ('ThatMgmt API') with a clear scope: reachability. This distinguishes it from sibling tools like portfolio_health and domains_dns, which target different resources or concerns.

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?

The description gives a clear context for use ('verify setup') and notes the auth requirement ('No API key needed'). It does not explicitly mention when not to use it or name alternatives, but for a simple health-check tool the guidance is sufficient.

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