Skip to main content
Glama

validate_timeline

Read-onlyIdempotent

Validate schema, timings, local assets, and bounds before rendering to catch errors early and ensure consistent project output.

Instructions

Validate schema, timings, local assets and bounds before rendering.

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": "<timeline>"
    },
    "name": "validate_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so safety is covered. The description adds real behavioral value by naming the four validation dimensions (schema, timings, local assets, bounds), which tells the agent what class of problems it surfaces. It stops short of saying whether failures are reported as a list or raised as errors.

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?

One sentence, front-loaded with the verb and the checked dimensions, with no filler. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety profile. The remaining hole is the "timeline" argument, whose type and expected form are undocumented anywhere — a real risk of a malformed call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter "timeline" has zero schema description coverage and the description never clarifies what it is — a file path, a project ID, or an inline JSON string. With 0% coverage this is the description's job to compensate, and it does not.

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?

Uses a specific verb ("Validate") and enumerates exactly what is checked: schema, timings, local assets, and bounds. The phrase "before rendering" scopes it against render/export siblings, though it never names a sibling explicitly.

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?

"Before rendering" implies the point in the workflow where this tool belongs, which is genuine usage guidance. However, there is no explicit exclusion (e.g. how it differs from validate_export) and no statement of what to do on failure.

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