Skip to main content
Glama

crafty_api_info

Retrieve Crafty Controller API version details and message of the day without authentication requirements.

Instructions

Get Crafty Controller API version information and message of the day (MOTD). Does not require authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation and registration of the crafty_api_info tool. It calls the client.get("/") method to retrieve the API version and MOTD.
    server.tool(
      "crafty_api_info",
      "Get Crafty Controller API version information and message of the day (MOTD). Does not require authentication.",
      {},
      async () => {
        try {
          const data = await client.get("/");
          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 context by stating 'Does not require authentication,' which informs the agent about authentication needs—a key behavioral trait. It doesn't mention other aspects like rate limits or response format, but for a simple read-only tool with zero parameters, this is reasonably transparent without being misleading.

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 extremely concise and front-loaded: it states the purpose in the first part and adds an important behavioral note ('Does not require authentication') in the second. Every sentence earns its place by providing essential information without any waste, making it easy for an agent to parse quickly.

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 simplicity—0 parameters, no annotations, and no output schema—the description is fairly complete. It explains what the tool does and adds authentication context. However, it doesn't describe the return values (e.g., what format the API version and MOTD are in), which could be helpful since there's no output schema. For a low-complexity tool, this is a minor gap.

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 input schema has 0 parameters with 100% description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. It gets a baseline score of 4 because the schema fully covers the lack of parameters, and the description doesn't need to compensate for any gaps.

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 clearly states the tool's purpose: 'Get Crafty Controller API version information and message of the day (MOTD).' It specifies the verb ('Get') and the resources ('API version information' and 'MOTD'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'crafty_get_stats' or 'crafty_get_config', which might also retrieve information but about different resources.

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 provides some usage context by stating 'Does not require authentication,' which implies this tool can be used without login credentials, unlike tools such as 'crafty_login'. However, it doesn't offer explicit guidance on when to use this tool versus alternatives like 'crafty_get_stats' for server statistics or 'crafty_get_config' for configuration details, leaving the choice somewhat implied based on the resource needed.

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