Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

Add Posting Slot

add_posting_slot

Add a repeating posting slot to the weekly calendar.

Ask for weekday (or today/tomorrow) and local time (HH:MM, 24-hour) if missing. Optional tag_name such as value, fun, or random.

This changes the weekly template, not a single date. Confirm with the user before adding.

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": {
      "weekday": "<weekday>",
      "local_time": "<local_time>"
    },
    "name": "add_posting_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekdayYesmonday–sunday, or today/tomorrow.
tag_nameNoOptional slot tag name (value, fun, random, or a custom name).
tag_colorNoOptional hex color for the tag, e.g. #0033FF.
local_timeYesLocal time in HH:MM 24-hour format, e.g. 09:30.
social_setNoThe social set (brand) this is for: its name, id or one of its handles. Omit when the user has one set.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent. The description adds real value beyond that: it clarifies the change affects the weekly template rather than a single date, and it instructs confirmation before mutating. It does not address duplicate-slot behavior, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with the core action, then the input requirements, then the safety caveat. Slight overlap with schema descriptions but no filler.

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 five-parameter mutation with annotations and no output schema, the description covers the essential risk (template-level change, confirm first) and the required inputs. Minor gaps remain around duplicate handling and the social_set default, but nothing critical is missing.

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 all five parameters are already documented, including the tag_name examples and the today/tomorrow weekday option. The description largely restates schema content rather than adding format or edge-case meaning, so the baseline 3 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?

States a specific verb and resource ('Add a repeating posting slot') and scopes it to the weekly calendar, which separates it from the single-date concept. It does not explicitly name the sibling tools (update/remove/get posting slot), so differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

Gives concrete operational guidance: ask for weekday and local time if missing, and confirm with the user before adding. It does not state when to prefer update_posting_slot or remove_posting_slot, but the when-to-use context is clear.

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

All SupaBird toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources