Skip to main content
Glama

get_canonical

Read-onlyIdempotent

Retrieve curated facts, decisions, and strategy docs for a topic from canonical project and workspace memory, excluding ephemeral session checkpoints and resolving slug aliases.

Instructions

Query the canonical knowledge layer: returns curated facts, decisions, and strategy docs for a topic, merged from project_memories (key canonical:*) and workspace_memories (kind:canonical). Excludes ephemeral session-checkpoints. Slug aliases are resolved automatically (e.g. mesh-dev == evc-mesh). Use it for the curated answer on a topic; recall searches all memory, get_canonical_updates lists decisions broadcast since a time.

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": {
      "topic": "<topic>"
    },
    "name": "get_canonical"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic or keyword to search (e.g. 'auth middleware', 'evc-spark roadmap').
projectNoOptional project slug to narrow results (e.g. 'evc-mesh', 'evc-spark'). Aliases resolved automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the merge of project_memories (key canonical:*) and workspace_memories (kind:canonical), the exclusion of ephemeral session-checkpoints, and automatic slug alias resolution. It does not discuss result ordering or limits, keeping it short of a 5.

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?

Three sentences, front-loaded with what is returned before the source mechanics and the disambiguation. Dense but each clause carries information; the parenthetical source-key syntax is slightly technical for the general reader but earns its place.

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?

With no output schema, the description compensates by naming the content types returned (facts, decisions, strategy docs) and the sources merged. Combined with annotations and full schema coverage, an agent has what it needs to call this correctly; only result shape details like pagination or ordering are unstated.

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 100%, so both topic and project are already documented including the alias-resolution note. The description's alias example (mesh-dev == evc-mesh) largely restates what the schema says, adding only a hint that the topic query spans merged sources rather than one store.

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 (query) and resource (canonical knowledge layer), then enumerates the content returned: curated facts, decisions, and strategy docs. It also names the two underlying sources, so an agent can distinguish it from generic memory tools at a glance.

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 says "Use it for the curated answer on a topic" and routes competing intents: recall for all-memory search, get_canonical_updates for decisions broadcast since a time. Both alternatives are named with the condition that selects them, so nothing is left to inference.

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