Skip to main content
Glama

slickpic_status

Checks your Cotlet.dev account, credits, and SlickPic connection to confirm everything is ready before you manage or deliver photos.

Instructions

Check that your Cotlet.dev account and SlickPic are ready: account, credits and SlickPic 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": "slickpic_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?

No annotations are provided, so the description carries the full burden. It does disclose what is being verified (account, credits, connection), which is essentially the content of the result, but says nothing about whether the call is read-only, whether it requires authentication, whether checking consumes credits, or how failures are reported.

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 and the three checks stated up front. Minor redundancy in listing 'account' twice (once as Cotlet.dev account, once in the enumeration), but no wasted framing.

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 tool this is close to adequate, but with no output schema and no annotations the description is the only source of truth about the response shape, and it does not say whether the result is a per-item pass/fail, an error, or a remediation hint. A short note on the return format would close the gap.

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 disambiguate and no schema gap to compensate for. Baseline of 4 applies.

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 ('Check') and enumerates the concrete resources being verified: account, credits, and SlickPic connection. It is clearly distinct in kind from the sibling browser-action tools (click, open, read, type), though it does not explicitly state that distinction.

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 by the framing of 'ready' — an agent can infer this is a preflight/diagnostic call, but nothing states when to run it, when not to, or what to do with the result. No alternatives or prerequisites are mentioned.

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