Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Warmup status and recent logs

get_account_warmup_status
Read-onlyIdempotent

Retrieve an account's warmup status, recent logs, today's schedule and progress, and upcoming sessions to monitor warmup performance and catch issues.

Instructions

Warmup status and recent logs. Required API key scope: accounts:read. GET /accounts/{id}/warmup-logs Last 50 logs, today's schedule and progress, and upcoming warmup sessions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_account_warmup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real value beyond that: the required API key scope accounts:read, the underlying endpoint, and the exact shape of what is returned (50-log cap, today's schedule, upcoming sessions).

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?

Four short lines, front-loaded with purpose, then auth scope, then endpoint, then payload detail. No filler sentences; the only redundancy is the title echoing the first line.

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 single-parameter read tool with no output schema, the description usefully compensates by describing the return payload and auth requirement. It is incomplete on the one thing that matters most given the sibling set: how this differs from get_account_warmup_history.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the schema text for `id` is only 'Path parameter `id`' — a tautology. The description never states that `id` is the account identifier, though the GET path `/accounts/{id}/warmup-logs` hints at it.

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 concrete resource (account warmup status plus recent logs) and enumerates the payload: last 50 logs, today's schedule and progress, upcoming sessions. It stops short of differentiating from the closely related sibling get_account_warmup_history, so an agent must guess which one to open.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. With a near-duplicate sibling (get_account_warmup_history) in the toolset, the description gives no rule for choosing between them, leaving selection to inference from the payload list.

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

Deploy Server

Other Tools