Skip to main content
Glama

tumblr_status

Verify your Cotlet.dev account, available credits, and Tumblr connection before using Tumblr workflows, so you can confirm setup is ready.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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; it does disclose the three things being verified (account, credits, Tumblr connection), which is the key behavioral content for a readiness check. It does not say whether the call has side effects, what happens on failure, or whether credits are consumed by the check itself.

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; the colon-list of checked items is an efficient structure. Minor awkwardness in the phrasing "account and Tumblr are ready: account, credits and Tumblr connection" repeats the word "account".

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter status tool with no output schema, the description covers the essential information: what is verified. An agent knows enough to call it and interpret a pass/fail, though it could be clearer about what a failing result looks like or what to do next.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no spurious argument detail.

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 a concrete resource set: account, credits, and Tumblr connection status. It is clearly a preflight/readiness tool, which distinguishes it from the action-oriented siblings (click, type, open, read), though it never names those siblings explicitly.

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 Tumblr operations, since it verifies readiness. There is no explicit when-to-use, when-not-to-use, or pointing to an alternative tool when the check fails.

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