Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Format Accessibility Summary

format_accessibility_summary
Read-only

Converts parsed accessibility violations into a clear, human-readable summary to help you quickly review and understand Canvas course accessibility issues.

Instructions

Format parsed violations into a human-readable summary.

Input Schema

NameRequiredDescriptionDefault
violations_jsonYesJSON string from parse_ufixit_violations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed7 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / violations_json / description
      Added value: +"JSON string from parse_ufixit_violations"
    • removedInput schema / properties / violations_json / title
      Removed value: -"Violations Json"
    • removedInput schema / title
      Removed value: -"format_accessibility_summaryArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"format_accessibility_summaryOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the input source and transformation goal, but it does not describe the summary's format, grouping, or contents, which are relevant since there is no output schema.

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 with no filler. Every word contributes to identifying the action and output.

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 simple one-parameter formatter with complete schema coverage and a read-only annotation, the description supplies enough context to invoke the tool correctly. It is slightly incomplete in not describing the summary's shape, but that is a minor gap given the tool's narrow purpose.

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%, and the parameter description already explains that violations_json is the JSON string from parse_ufixit_violations. The tool description repeats the same source without adding further semantics such as expected structure or validation constraints.

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?

The description gives a specific verb ('Format') and resource ('parsed violations') with the output type ('human-readable summary'). It clearly identifies the transformation but does not explicitly distinguish this tool from siblings like parse_ufixit_violations or fetch_ufixit_report.

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?

Usage is implied by 'parsed violations' and the parameter description referencing parse_ufixit_violations, so an agent can infer it should be called after parsing. However, the description does not state when to use this versus alternatives or any exclusions.

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

Deploy Server

Other Tools