Skip to main content
Glama

tracker_status

Read-only

Checks Tracker API authentication and the configured organization ID without exposing credentials or personal profile data; use it to confirm connection setup, not per-issue access.

Instructions

Check Tracker API authentication and configured organization ID, without returning credentials or personal profile data. Does not verify access to every issue.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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=true, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses what will not be returned (credentials, profile data) and what the check does not prove (per-issue access), which prevents an agent from over-trusting a success result.

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 no filler, and the core function is stated first with the caveat second. Every clause carries information an agent would otherwise have to guess.

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 read-only diagnostic with no output schema, the definition covers what is checked and what is deliberately withheld. The remaining gap is that it never hints at the result shape (e.g., boolean versus a status string), which an agent must discover by calling 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, so the schema carries no semantics to supplement; the baseline of 4 applies. Nothing in the description misrepresents how it is invoked.

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 target (check Tracker API authentication and configured organization ID) and scopes the output by exclusion (no credentials or personal profile data). It is unambiguous and clearly not one of the issue-oriented siblings, though it does not name an alternative explicitly.

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

Usage Guidelines3/5

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

Use is implied as a connectivity/config sanity check, and the closing sentence usefully states a limitation (does not verify access to every issue). However, there is no explicit when-to-use trigger or guidance on what to call instead when the check fails.

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