Skip to main content
Glama
osbytes

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set default intro/outro

set_default_bumper
Idempotent

Set a library intro or outro as the default for new projects; pass null to clear it. Existing projects keep their bumpers.

Instructions

Make a library item your default intro or outro for projects you create from now on (assetId null clears it). Existing projects keep theirs; to change one use set_project_bumpers. Returns { ok }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYesWhich default to set
assetIdYesLibrary asset id (list_bumpers), or null for no default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / assetId / description
      Added value: +"Library asset id (list_bumpers), or null for no default"
    • addedInput schema / properties / slot / description
      Added value: +"Which default to set"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only provide idempotentHint; the description adds valuable scope behavior (future-only effect) and the null-clears semantic. It also mentions the return shape, though it doesn't note auth requirements or what happens to already-defaulted rows.

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?

Three short clauses, front-loaded with the main action, then the scope caveat, then the return shape — zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-param idempotent setter with no output schema, the description covers scope, clear semantics, alternative tool, and return value. Nothing essential is missing.

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 baseline is 3; the description adds the 'assetId null clears it' semantic that clarifies the anyOf-null branch beyond the schema's terse wording.

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?

States a specific verb (make default) and resource (intro/outro bumper), and clearly scopes it to future projects versus existing ones, distinguishing it from set_project_bumpers.

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

Usage Guidelines5/5

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

Explicitly says it affects projects created from now on, tells the agent existing projects are unchanged, and names the alternative (set_project_bumpers) for that case.

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