Skip to main content
Glama

Get timeline

get_timeline
Read-onlyIdempotent

Returns a timeline with all its events and periods and their ids. Public timelines can be read without sign-in; other timelines only by their owner.

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

Input Schema

NameRequiredDescriptionDefault
timeline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new context by disclosing the authorization model (public vs owner-only access). It does not mention error behavior for inaccessible or nonexistent ids, which would have completed the picture.

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 short sentences with zero filler: the return shape comes first, the access constraint second. Every clause carries information an agent needs.

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 one-parameter read with no output schema, the description adequately covers return contents, access rules and the required id. Missing only failure-mode behavior for private or nonexistent timelines.

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 description coverage is 0% and the single parameter timeline_id is undocumented in the schema, so the description must compensate — but it only alludes to "a timeline" without explaining the id's source or format. Given the parameter is a self-evident integer identifier, the baseline 3 applies rather than a penalty.

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?

States a specific verb and resource ("Returns a timeline") plus the payload scope ("all its events and periods and their ids"), which separates it from list_my_timelines and search_timelines that return timeline collections rather than full contents. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

The second sentence gives an operational condition — public timelines need no sign-in, others are owner-only — which tells the agent when a call will succeed. However, there is no guidance on choosing between get_timeline and list_my_timelines/search_timelines, nor any note on what to do when the id is unknown.

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