Skip to main content
Glama

flickr_status

Check that your Cotlet.dev account, credits, and Flickr connection are ready before using Flickr tools.

Instructions

Check that your Cotlet.dev account and Flickr are ready: account, credits and Flickr 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": "flickr_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 the three things inspected (account, credits, Flickr connection), which implies a read-only diagnostic, but it does not state the return shape, whether the check costs credits, or what conditions count as 'not ready'.

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?

One front-loaded sentence with the verb first and the enumerated checks trailing. The colon list slightly restates the opening clause, but there is no meaningful waste.

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-param status tool the description covers what is inspected, but with no output schema the agent has no idea whether the result is a boolean, a status enum, or a message per check, or how to interpret a failure.

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 the baseline is 4. There is no parameter semantics to explain and the description correctly describes a no-input operation.

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 gives a specific verb ('Check') and a concrete object (account, credits, and Flickr connection readiness), which clearly separates it from the action siblings flickr_open, flickr_click, flickr_read, etc. It does not name a sibling alternative, but the diagnostic nature is unmistakable.

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: an agent can infer this should be run before attempting other flickr_* operations to verify prerequisites. There is no explicit 'use when', no statement of what to do on failure, and no named alternative.

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