Skip to main content
Glama

Owned-core health check

health

Check the owned-core MCP server's status and confirm it is reachable end-to-end.

Instructions

Return the owned-core server's health/status. Call this to confirm the owned-core MCP server is reachable end-to-end.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It establishes that this is a probe of server reachability, which implies a harmless read, but it never explicitly says the call is non-mutating or describes what a 'status' payload contains, how failures surface, or whether repeated calls have cost.

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 short sentences with the capability stated first and the use case second. There is no filler, no restatement of the title, and nothing that could be trimmed without losing information.

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 ping-style tool with no output schema and no annotations, the definition covers what it does and when to use it. The one meaningful omission is any hint about the shape or interpretation of the returned status, which matters because no output schema exists to document it.

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, which is the baseline case for a 4. There is nothing extra the description could meaningfully add about input semantics, and the empty schema matches the description's framing as a no-argument probe.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Return the owned-core server's health/status.' That is unambiguous and clearly distinct from the memory-editing siblings. It stops short of explicitly contrasting itself with any alternative, but the purpose itself is easy to grasp.

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?

'Call this to confirm the owned-core MCP server is reachable end-to-end' gives a clear triggering condition rather than leaving usage implied. It does not state when not to call it, or that other tools should be used once reachability is established, so it falls short of full alternative routing.

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