Skip to main content
Glama

ontraccr_status

Check Cotlet.dev account status, available credits, and Ontraccr connection to confirm the integration is ready before using Ontraccr actions.

Instructions

Check that your Cotlet.dev account and Ontraccr are ready: account, credits and Ontraccr 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": "ontraccr_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 disclosure burden. It does add real behavioral content by naming the three things verified (account, credits, Ontraccr connection), which tells the agent this is a non-mutating readiness probe. It stops short of disclosing what happens on failure, whether a network/auth call is made, or what the response looks like, which matters for a zero-annotation tool.

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?

It is a single compact sentence with the object of the check front-loaded, and every clause earns its place by enumerating what is verified. The colon list is slightly redundant with the opening phrase, but the phrasing is efficient overall.

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?

For a zero-parameter readiness check the description covers what is inspected, but with no output schema the agent has no idea what the result shape is — a boolean, per-item statuses, or credit counts. Adding one clause about the return would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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-level meaning for the description to add and the baseline applies. The description does not mislead about inputs, and nothing about parameters is missing.

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 states a specific verb ('Check') and a concrete subject: readiness of the Cotlet.dev account, credits, and the Ontraccr connection. That is clearly distinguishable from the sibling tools, which are UI actions (click, type, open, read), so an agent can identify this as the diagnostic/health-check tool. It is not quite a 5 because the phrasing 'are ready' is looser than a precise statement of what is validated.

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?

The framing ('Check that ... are ready') implies a pre-flight verification step before doing real work with Ontraccr, which is useful implied guidance. However, it never states when to call this versus the other sibling tools, nor any prerequisites or thresholds (e.g., call before or after connecting). Usage is inferable but not explicit.

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