Clawhard Studio

Create a live day-of schedule page

runsheet_create_schedule

Use when the user wants a shareable run-of-show or day-of schedule for a wedding, conference, shoot or other event that guests or crew can open on their phone and that updates live when edited. Creates the page and returns a view link to share with everyone and a private edit link to keep. Start from a template (wedding, conf, shoot, blank) or pass your own items. Example: {"name": "Maya and Sam wedding", "date": "2026-09-12", "timezone": "America/New_York", "template": "wedding"} or {"name": "Offsite", "items": [{"time": "09:00", "title": "Welcome", "duration_minutes": 30}]}. Each call creates a new saved page.

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": "runsheet_create_schedule"
  }
}

Input Schema

Name	Required	Description
`date`	No	YYYY-MM-DD
`name`	No	Event name.
`items`	No	Schedule slots.
`template`	No	Starter schedule. Ignored if items are given.
`timezone`	No	IANA time zone, e.g. America/New_York. Default UTC.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description's added value is the live-updating behavior, the two returned links, and the fact that the edit link is private and should be kept. That is meaningful context beyond the annotations, though it says nothing about auth/account requirements or limits on the generated page.

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?

It is front-loaded with the trigger, then behavior, then examples — a sensible order with no filler sentences. The two inline JSON examples take up a lot of space and partially restate schema fields, but they earn their place by disambiguating the template-vs-items path.

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?

With five optional parameters and no output schema, the description correctly spends effort describing return values (view link, edit link) and the live-update nature of the page. It is nearly complete; the only omission is any note on authorization, ownership, or how many pages a user can create.

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?

Schema coverage is 100%, so the field-level meanings are already documented. The description still adds value by showing two realistic call shapes, demonstrating that template and items are alternative starting points and illustrating how name/date/timezone combine. It reinforces rather than merely repeats the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and artifact: it creates a shareable, live-updating day-of schedule page that guests open on a phone. It also states the concrete outcome — a public view link plus a private edit link — so an agent knows exactly what it gets back, not just that something is 'created'.

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?

It opens with an explicit trigger ('Use when the user wants a shareable run-of-show or day-of schedule') and enumerates the event types that qualify. It also warns that every call creates a new saved page, which discourages accidental duplicate creation. There are no sibling tools, so the absence of named alternatives is not a real gap.

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

All Clawhard Studio tools Inspect

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

Need Help?