Skip to main content
Glama

Add a posting slot

clipember_add_posting_slot

Add a preferred posting time to an account: local time (HH:MM, 24-hour) in an IANA time zone, on chosen weekdays (1 = Monday … 7 = Sunday; default every day). The time stays the same local time across daylight-saving changes.

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": {
      "connectionId": "<connectionId>",
      "time": "<time>",
      "timezone": "<timezone>"
    },
    "name": "clipember_add_posting_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesLocal time, HH:MM, e.g. 09:30
timezoneYesIANA time zone, e.g. Europe/Kyiv
weekdaysNo
connectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe-but-mutating profile (readOnly false, destructive false, idempotent false), so the description's real contribution is the DST note — the time is stored as local time and follows daylight-saving shifts — which is genuine behavior no structured field states. It also discloses that weekdays defaults to every day, filling a gap left by the non-required schema field. It stops short of duplicate-handling, permission needs, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and then the three input semantics in the order an agent needs them. No filler or restatement of the tool name beyond the opening clause.

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 small mutation tool with no output schema, the description covers the inputs adequately but is silent on connectionId's meaning and on the practical edge cases an agent will hit: an existing slot at the same time, whether the result returns an id, and whether scheduling permissions are required. Those omissions are the difference between adequate and 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?

With only 50% schema coverage, the description compensates well: it restates the 24-hour HH:MM format, confirms the IANA time zone requirement, and adds the weekday numbering convention (1 = Monday … 7 = Sunday) plus the every-day default, none of which appear in the schema. Only connectionId is left unexplained.

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?

"Add a preferred posting time to an account" gives a specific verb and resource, and the rest of the sentence pins down the three key dimensions (time, timezone, weekdays). It is clearly distinct from list/delete siblings by name alone, but it never explicitly contrasts itself with them.

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 is the tool for creating a recurring posting preference rather than listing or removing one. There is no explicit when-to-use/when-not guidance, no mention of what happens if a slot at that time already exists, and no prerequisite about the account connection beyond the required connectionId.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources