Skip to main content
Glama

Raziel

by io.github.tide-foundation

tide_canon

Read-only

Read a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCanon file name. Available: agent-authority, anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, tidify-compatibility, troubleshooting, ux-states, verifiable-claims, version-policy

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Canon file name. Available: agent-authority, anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, verifiable-claims, version-policy"New value: +"Canon file name. Available: agent-authority, anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, tidify-compatibility, troubleshooting, ux-states, verifiable-claims, version-policy"
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, verifiable-claims, version-policy"New value: +"Canon file name. Available: agent-authority, anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, verifiable-claims, version-policy"
  3. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, version-policy"New value: +"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, verifiable-claims, version-policy"
  4. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, version-policy"New value: +"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, ux-states, version-policy"
  5. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Canon file name. Available: anti-patterns, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, version-policy"New value: +"Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, security-gap-mapping, security-runtime-probes, tide-neutralization, tidecloak-bootstrap, tidecloak-endpoints, troubleshooting, version-policy"
  6. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds the list of canon file types but does not describe return format, error handling, or other behavioral nuances. It provides only minimal additional context beyond annotations.

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?

The description is a single, front-loaded sentence that directly states the tool's purpose. It is concise and free of unnecessary wording, with the 'etc.' being acceptable given the complete enumeration in the schema.

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?

Given the tool's low complexity (one parameter, no output schema), the description plus schema is sufficient for an agent to select and invoke it correctly. The only minor gap is that it does not explicitly state the return value, but 'Read' strongly implies the file content is returned.

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?

The input schema has 100% coverage for the single parameter 'name', including a full list of allowed values. The description merely repeats a subset of these values (e.g., invariants, concepts) without adding any new syntax or semantic detail. Baseline score of 3 applies when schema covers the parameter fully.

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 clearly states the verb 'Read' and the resource 'canon file', and lists examples of file types. This distinguishes it from sibling tide_* tools by being the only one focused on reading canon files.

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 description implies usage (when you need to read a canon file) but does not explicitly state when to use it over alternatives or mention any exclusions. No sibling tool is referenced as an alternative.

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

All Raziel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: reading specific document types (adapter, canon, gaps, playbook, etc.), performing assessments (blast_radius, security_analysis), branding, deployment decision, and listing content. However, some reading tools like tide_canon and tide_gaps could be confused, and the multiple scenario-related tools (scenario, bootstrap, manifest, roles) require careful reading of descriptions to differentiate.

Naming Consistency4/5

All tools use the 'tide_' prefix with snake_case, which provides a strong pattern. However, the naming mixes nouns (tide_canon, tide_gaps) with verb phrases (tide_choose_playbook, tide_list), and some tools like tide_dpop_asset are less intuitive. The pattern is mostly consistent but not strictly verb_noun.

Tool Count3/5

With 19 tools, the set is on the higher end for a single server. While many are necessary for the broad scope of reading various reference materials and performing analyses, the count feels slightly excessive. A few tools could be consolidated or removed to improve focus.

Completeness4/5

The tool surface covers reading all major reference documents, performing security assessments, branding, deployment decisions, and scenario matching. For the stated purpose of a 'Tide agent pack', it appears comprehensive. Minor gaps might include a tool for overall system health or status, but the core workflows are well-covered.

Resources