Skip to main content
Glama

Set timeline access

set_access
DestructiveIdempotent

Makes a timeline the user owns public, visible by link only, or private. Link and private access are part of Time.Graphics Premium; without it, the tool returns an error with a link to the plans page.

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": {
      "timeline_id": "<timeline_id>",
      "access": "<access>"
    },
    "name": "set_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessYes
timeline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description does not need to re-state safety. It adds genuinely new behavior the annotations lack: the ownership precondition and the plan-gated failure mode with an error and plans link. It never addresses what the previous access level was or whether a downgrade can be undone, which matters for a destructive operation.

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?

Two sentences, no wasted words, with the three access modes front-loaded and the Premium caveat second. The structure matches how an agent reads: what it does, then what blocks it.

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 two-parameter mutation tool with no output schema and rich annotations, the description covers purpose, precondition, access semantics and the premium blocker. The remaining gap is what the call returns on success and whether prior access state is recoverable.

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 0%, so the description must carry both parameters. It does explain the meaning of the access values ('public', 'visible by link only', 'private'), which usefully maps to the enum, but timeline_id is never explained and no constraint such as who owns the timeline, the type, or the format is given for it.

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 gives a specific verb ('Makes... public/link/private') applied to a specific resource ('a timeline the user owns'), and it enumerates the three target states. No sibling tool touches access settings, so an agent can easily distinguish it from create_timeline or update_event.

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 description sets a clear precondition ('a timeline the user owns') and a clear failure condition (link/private require Premium, otherwise an error with a plans link). It names no alternative tool, but no sibling is a plausible substitute, so the missing exclusions cost little.

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