Skip to main content
Glama

get_canonical_updates

Read-onlyIdempotent

Fetch canonical decisions broadcast since a given time to catch up at session start, returning only public records targeted to you or all agents.

Instructions

Fetch canonical decisions broadcast since a given time. Returns only privacy:public records targeted at you or all agents. A change feed for session start; get_canonical searches the canonical layer by topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_canonical_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoYour agent slug (e.g. 'alice'). Used to filter propagate_to:<slug> records. Omit to get only propagate_to:all records.
scopeNoOptional project UUID to restrict to project-scoped decisions.
sinceNoRFC3339 cursor. Defaults to your previous session's start time (server-resolved). Omit on first call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover safety profile (readOnly, idempotent, non-destructive, closed-world), so credit is for added context: the privacy:public restriction and the targeted-at-you-or-all-agents filter are genuinely useful disclosure. Beyond that, it is silent on ordering, pagination, and volume of the feed, which matter for a change feed an agent polls at session start.

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 sentences, front-loaded with the action and scope, then the sibling disambiguation. No filler or repetition.

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?

No output schema exists, so the description carries some burden, and it does name what comes back (privacy:public, targeted records) and the cursor default. It stops short of describing record shape or feed ordering, a minor gap for a three-optional-parameter read tool.

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 100%, so the schema already documents agent, scope, and since including the server-resolved default. The description only echoes 'since a given time' and the targeting semantics already stated in the agent parameter, adding little.

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 and resource ('Fetch canonical decisions broadcast since a given time') plus the exact filtering scope (privacy:public records targeted at you or all agents). It also distinguishes itself from the similar-sounding sibling get_canonical by naming its different access pattern.

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 frames usage as 'a change feed for session start' and routes topical lookups to get_canonical instead. The filtering scope statement also implies when-not (records not targeted at you or all agents are excluded).

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