Skip to main content
Glama

fitune_status

Check your Cotlet.dev account, credits, and Fitune connection to confirm your studio setup is ready before using Fitune tools.

Instructions

Check that your Cotlet.dev account and Fitune are ready: account, credits and Fitune connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It implies a read-only check by naming the resources inspected, but it never says whether it performs live network/API calls, what happens on partial failure (e.g., account valid but Fitune disconnected), or how results are surfaced. For a diagnostic tool whose entire value is reporting failures, that is a significant gap.

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?

A single front-loaded sentence with no wasted words, and the three checked items are listed compactly. It is arguably a touch terse for a diagnostic tool, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no params, no nested objects, no output schema), so the description covers the what. However, because no output schema exists, an agent has no idea what a status response looks like or how failures are reported — the one piece of information most needed before relying on this tool.

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 is no parameter semantics to document; the baseline for a no-param tool is 4. The description correctly implies no input is needed to run the check.

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?

States a specific verb ("Check") and enumerates the resources verified: account, credits, and Fitune connection. It is clearly distinguishable from the action siblings (fitune_open, fitune_click, fitune_read), but "ready" is left undefined and the description doesn't say whether it returns per-item statuses or a single verdict.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative is named. Usage is only implied by the phrase "ready" — an agent would infer this as a preflight check before calling the other fitune_* tools, but that inference is never stated.

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