Skip to main content
Glama

Health Check

health
Read-only

Verifies your TestDino token, returns account identity, and lists accessible organizations and projects with IDs. Use it to find a projectId or orgId and resolve auth or PROJECT_NOT_FOUND errors.

Instructions

Verifies your TestDino token, returns your account identity, and lists the organizations and projects you can access with their ids and names (orgName, projectName). Call it when you need a projectId or orgId you do not have yet. Most tools take a projectId from this list (match by projectName if the user gives a name); get_org_details takes an orgId. Reuse the id for later calls instead of calling this again. Each organization also reports your role in it (owner, admin, member, billing, or viewer) so you can tell the user what they can do there — treat it as informational, not a security guarantee. Wildcard scopes surface as projects: { allProjects: true } with no per-project names — for those, ask the user which projectId to use, or call a listing tool. Recently-renamed orgs/projects may show the old name for up to 30s (registry poll cadence). Also call this whenever you get a PROJECT_NOT_FOUND or auth error from another tool — it will tell you which projects are actually accessible.

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. Changed2 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / required
      Removed value: -[]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnlyHint=true), and the description adds substantial context beyond that: role fields are informational and not a security guarantee, wildcard scopes appear as `projects: { allProjects: true }` with no names, and renamed orgs/projects may show stale names for up to 30s. That is exactly the kind of behavioral nuance annotations cannot express.

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: the first sentence says what it returns, and later sentences build outward to usage and edge cases in a logical order. It is long for a health-check tool, but nearly every clause carries operational value; the wildcard and staleness caveats in particular prevent real mistakes.

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?

There is no output schema, so the description must carry return values, and it does: identity, orgs, projects, ids, names, role, and the allProjects wildcard shape. It also covers the failure path (auth/PROJECT_NOT_FOUND) and the staleness window, leaving nothing an agent needs in order to call it correctly.

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 there are no input semantics to explain; baseline 4 applies. The description instead spends its effort on output shape (orgName, projectName, role, allProjects), which is useful given there is no output schema, but that value is credited under completeness rather than parameter semantics.

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 opens with a specific three-part verb+resource statement: verifies the token, returns account identity, and lists organizations/projects with ids and names. It explicitly distinguishes itself from get_org_details (takes an orgId) and from a listing tool for wildcard scopes, so an agent can pick it without opening a schema.

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?

It gives explicit when-to-use conditions ('when you need a projectId or orgId you do not have yet'), tells the agent how to map a projectName to a projectId, names get_org_details as the orgId consumer, and adds a recovery rule: call this on PROJECT_NOT_FOUND or auth errors. It even says when to reuse a cached id rather than calling again.

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