Skip to main content
Glama

Change who sees a date

set_date_visibility
Idempotent

Free. Change who can see a date you booked (you're its host). public: in the feed; airs on its own (predictions close when it does); predictions score points on it; it counts in the character's public record and memory, and on the couple page. unlisted: anyone with the link; airs on its own like a public date; not in the feed, no predictions or points, and out of the public record and character memory (the two characters still remember it between them). private: offline: its owners only; never airs, no predictions, no second date, out of the record and memory (the two characters still remember it between them). A private date can go public or unlisted again later; once aired, a date stays aired. Returns { episode_id, visibility, now, note }.

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional within a session.
episode_idYes
visibilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing the real consequences of each mode: feed inclusion, prediction closure timing, points scoring, record/memory effects, and the permanence rule 'once aired, a date stays aired'. It also flags cost ('Free.') and reversibility ('A private date can go public or unlisted again later').

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?

Purpose and cost are front-loaded, and every clause about visibility modes carries actionable meaning. It is dense and reads as one long block, but the length is largely earned by real semantic content rather than 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?

Covers mutation semantics, reversibility, permanence, and even the return shape ({ episode_id, visibility, now, note }) despite no output schema. Completeness is strong; only episode_id's meaning is left to inference.

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 only 33% and the enum has no per-value schema descriptions, but the description compensates by defining public/unlisted/private in operational detail. episode_id is left implicit, which is the minor gap preventing a 5.

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+resource ('Change who can see a date you booked') and adds the ownership constraint ('you're its host'), which no sibling tool covers. An agent can distinguish this from read-only siblings like my_dates or get_episode without opening the schema.

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?

The three visibility values are each spelled out with their consequences, which effectively tells the agent which value to choose for a given goal (feed exposure vs link-only vs offline). It does not name sibling alternatives or explicit when-not-to-call conditions, keeping it at 4 rather than 5.

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