Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Canvas Tools

search_canvas_tools
Read-only

Search Canvas tools by keyword to locate registered MCP tools or TypeScript code-execution APIs, with names, signatures, or full details.

Instructions

Search available Canvas tools by keyword — both the registered MCP tools (e.g. list_peer_reviews, create_assignment) and the TypeScript code-execution API used by execute_typescript().

Input Schema

NameRequiredDescriptionDefault
queryNoSearch term to filter tools (empty = all)
detail_levelNo"names" (names/paths only), "signatures" (recommended), or "full" (fuller descriptions/file contents)signatures

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.0
    • changedInput schema / properties / detail_level / description
      Previous value: -"\"names\" (paths only), \"signatures\" (recommended), or \"full\" (complete file contents)"New value: +"\"names\" (names/paths only), \"signatures\" (recommended), or \"full\" (fuller descriptions/file contents)"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed9 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / detail_level / description
      Added value: +"\"names\" (paths only), \"signatures\" (recommended), or \"full\" (complete file contents)"
    • removedInput schema / properties / detail_level / title
      Removed value: -"Detail Level"
    • addedInput schema / properties / query / description
      Added value: +"Search term to filter tools (empty = all)"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_canvas_toolsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"search_canvas_toolsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The description goes beyond the simple 'readOnlyHint' annotation by disclosing a critical technical behavior: the search indexes not just tool names, but the TypeScript code and API usage of the `execute_typescript()` function. This is a high-value piece of context not covered by structured metadata.

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 definition is extremely concise and front-loads the most important information—the search scope—in a single, impactful sentence without wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Since no output schema exists, the description is incomplete as it does not specify what the tool returns (e.g., a list of tool strings, structured JSON results). It describes the input behavior but not the output contract.

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 schema description coverage is 100%, providing sufficient detail for both the 'query' and 'detail_level' parameters. The description does not add unique semantic meaning beyond what is already provided in the input schema descriptions.

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 tool clearly states its purpose as searching available Canvas tools by keyword. Crucially, it distinguishes itself by specifying the scope encompasses both 'registered MCP tools' and the 'TypeScript code-execution API', separating it from the functional tools listed as siblings.

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 doesn't explicitly state when to use this tool versus the thousands of specific action-oriented tools in the sibling list. The usage is implied (use this when trying to discover tools or their API usage) but not explicitly defined.

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