Skip to main content
Glama

pic_time_status

Checks your Cotlet.dev account, available credits, and Pic-Time connection so you can confirm readiness before using Pic-Time tools.

Instructions

Check that your Cotlet.dev account and Pic-Time are ready: account, credits and Pic-Time 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": "pic_time_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, the description carries the full burden: "Check" implies a non-mutating read, but the definition never confirms this is safe/read-only, never says whether it performs network calls or can hang on a disconnected account, and never indicates what the result looks like. It does add useful scope detail (three distinct things verified), which keeps it above a 2.

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 the verb first and the checked items enumerated after the colon. No wasted wording, though the colon-list is slightly clipped and could read as compressed.

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 simple zero-parameter status check this is close to adequate, but with no output schema and no annotations the agent gets no sense of the return shape (booleans? per-item status?) or failure semantics. One more sentence covering the response and any required auth would make it complete.

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 nothing for the description to compensate for; baseline 4 applies. The description correctly implies no inputs are needed.

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 enumerated resources (account, credits, Pic-Time connection), which clearly distinguishes this diagnostic tool from the UI-action siblings like pic_time_click and pic_time_open. It stops short of 5 only because "ready" is left slightly loose about what constitutes not-ready.

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 word "ready" implies this is a preflight check to run before other Pic-Time operations, but the description never says that explicitly, nor does it describe what to do if a check fails or which sibling to use afterward. Usage is implied rather than stated.

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