Skip to main content
Glama

crafty_list_schemas

List all available JSON schema names in Crafty Controller without requiring authentication.

Instructions

List all available JSON schema names in Crafty Controller. Does not require authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the crafty_list_schemas tool, which fetches JSON schema information from the Crafty Controller.
    server.tool(
      "crafty_list_schemas",
      "List all available JSON schema names in Crafty Controller. Does not require authentication.",
      {},
      async () => {
        try {
          const data = await client.get("/jsonschema");
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds value by specifying that authentication is not required, which is a key behavioral trait not inferable from the input schema alone. However, it lacks details on output format (e.g., list structure, pagination) or potential errors, leaving some behavioral aspects uncovered.

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, efficient sentence that front-loads the core purpose ('List all available JSON schema names in Crafty Controller') and adds a crucial behavioral note ('Does not require authentication') without any wasted words. Every part of the sentence provides essential information.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is reasonably complete for its purpose. However, it lacks details on the return values (e.g., format of the list, error conditions), which would be helpful since there is no output schema. This gap prevents a higher score despite the simple context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to compensate for any parameter gaps, as there are none. It appropriately focuses on the tool's purpose without redundant parameter information, earning a baseline score of 4 for zero-parameter tools.

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 specific action ('List all available JSON schema names') and resource ('in Crafty Controller'), distinguishing it from siblings like crafty_get_schema (which retrieves a specific schema) and other list tools (e.g., server_list, user_list) that target different resources. It precisely defines the scope without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by stating 'Does not require authentication,' which is useful for understanding prerequisites. However, it does not explicitly mention when to use this tool versus alternatives like crafty_get_schema (for detailed schema retrieval) or other list tools, leaving some sibling differentiation implicit rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HadiCherkaoui/crafty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server