Skip to main content
Glama

pike13_status

Checks Cotlet.dev account readiness, available credits, and Pike13 connection status so you can confirm the integration is set up before running workflows.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden; it does communicate that this is a non-mutating readiness check scoped to three concerns. However, it says nothing about what a result contains, how failures are surfaced, or whether calling it has any side effects.

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 filler, and the enumerated checks come after the verb. Slightly awkward phrasing ("your Cotlet.dev account and Pike13 are ready") but nothing that wastes space.

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 no-param diagnostic tool the description should say what the check returns and how a negative result looks, especially since there is no output schema to fall back on. It names the checks but leaves the result semantics entirely unspecified.

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 for a 4 – there is nothing for the description to disambiguate. It correctly signals a no-input call.

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 three things verified: account, credits, and Pike13 connection. It is clearly distinguishable from the action-oriented siblings (click, close, open, read, type), though it never explicitly contrasts itself with them.

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?

Usage is only implied through the phrase "ready" – an agent can infer this is a pre-flight/health check to run before acting, but there is no statement of when to call it, when not to, or what to do on failure. No alternative tool is referenced.

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