Skip to main content
Glama
Sign In

Ringske

by be.ringske
OverviewDiscussionsAdmin

Add run-of-show item

add-schedule-item

Adds an item to the run of show (draaiboek) of the wedding day, e.g. "14:00 Ceremony". Items marked for_guests also appear in the programme on the wedding website.

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": {
      "title": "<title>"
    },
    "name": "add-schedule-item"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
ownerNoWho takes care of it, e.g. "Best man" or "DJ".
titleYes
locationNo
title_enNoEnglish title for the guest programme on the website.
moment_idNoThe moment it belongs to (list-moments); null for none.
starts_atNoStart time HH:MM, e.g. "14:30". 00:00–05:59 counts as the night after.
vendor_idNoA vendor from list-vendors; null to unlink.
for_guestsNoShown in the programme on the wedding website.
duration_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a non-readonly, non-destructive, closed-world creation tool. The description adds the guest-website visibility effect for for_guests items, but this is also captured in the schema, and it does not mention permissions, duplicate handling, or response behavior.

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?

The description is two front-loaded sentences with a compact, helpful example. The second sentence largely restates schema information but does call out the guest-visible consequence clearly.

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 10-parameter creation tool with no output schema, the description establishes the core purpose and one important side effect. It does not cover the remaining parameter semantics or clarify when to use the update/delete/get siblings, so it is adequate but not comprehensive.

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 description coverage is moderate at 60%, with useful descriptions for owner, title_en, moment_id, starts_at, vendor_id, and for_guests. The description reinforces the title example and guest-visibility meaning, but leaves parameters such as notes, location, and duration_minutes without additional guidance.

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 states a specific verb and resource: adds an item to the run of show for the wedding day. The example clarifies the intended item format, but it does not explicitly distinguish this from update-schedule-item or delete-schedule-item.

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?

Creation is implied by 'Adds' and the run-of-show context, so the basic use case is understandable. However, there is no explicit guidance on when to use this versus update-schedule-item, delete-schedule-item, or get-schedule, and no prerequisites or exclusions are stated.

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

All Ringske 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