Skip to main content
Glama
chongzixuan-ai

AI Humanizer MCP Server

detect

Identify AI-generated text using detection tools and provide detailed analysis results through a task-specific URL.

Instructions

Detect whether the text is AI-generated.Show to user the task detail url. Extract the taskId field, then concatenate the link in the following format: https://pre-www.text2go.ai/?utm_source=claude_mcp&taskId={taskId}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYes
detectionTypeListYes

Implementation Reference

  • Handler for the 'detect' tool: parses input arguments using Zod schema, sends POST request to AI detection API endpoint, handles response or error, and returns JSON stringified result.
    if (name === "detect") {
      const argument = AiDetectArgumentSchema.parse(args);
    
      const detectUrl = `${API_BASE}/rewrite/text-detection`;
      const detectData = await makeRequest<AiDetectResponse>(detectUrl, argument);
    
      if (!detectData) {
        return {
          content: [
            {
              type: "text",
              text: "Failed to retrieve alerts data",
            },
          ],
        };
      }
    
      const responseData = {
        ...detectData
        ,text: undefined,
      };
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(responseData),
          },
        ],
      };
    } else {
  • src/index.ts:35-64 (registration)
    Registration of the 'detect' tool in the ListToolsRequestSchema handler, defining name, description, and JSON input schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
            {
                name: "detect",
                description: "Detect whether the text is AI-generated.Show to user the task detail url. Extract the taskId field, then concatenate the link in the following format: https://pre-www.text2go.ai/?utm_source=claude_mcp&taskId={taskId}",
                inputSchema: {
                  type: "object",
                  properties: {
                    type: {
                      type: "string",
                      enum: ["original_text"],
                    },
                    text: {
                      type: "string",
                    },
                    detectionTypeList: {
                      type: "array",
                      items: {
                        type: "string",
                        enum: ["COPYLEAKS", "HEMINGWAY"],
                      },
                    },
                  },
                  required: ["type", "text", "detectionTypeList"],
                },
              }
        ],
      };
    });
  • Zod schema (AiDetectArgumentSchema) for validating and parsing the input arguments to the 'detect' tool handler.
    const AiDetectArgumentSchema = z
      .object({
        type: z.enum(["original_text"]),
        text: z.string(),
        detectionTypeList: z.array(
          z.enum(["COPYLEAKS", "HEMINGWAY"])
        ),
      })
      .required();
  • Helper function 'makeRequest' used by the 'detect' handler to perform POST requests to the external API.
    async function makeRequest<T>(url: string, data?: any): Promise<T | null> {
      const headers = {
        "User-Agent": USER_AGENT,
        "Accept": "application/json",
        "Content-Type": "application/json"
      };
    
      try {
        const response = await fetch(url, {
          method: 'POST',
          headers,
          body: data ? JSON.stringify(data) : undefined
        });
        
        if (!response.ok) {
          throw new Error(`HTTP error! status: ${response.status}`);
        }
        return (await response.json()) as T;
      } catch (error) {
        console.error("Error making request:", error);
        return null;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions showing 'the task detail url' to the user and extracting/concatenating a taskId, which hints at some output behavior. However, it fails to describe critical aspects like what the detection result looks like, error conditions, or rate limits. The behavioral disclosure is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is poorly structured—it starts with the detection purpose but then abruptly shifts to URL construction instructions without clear connection. This creates confusion rather than clarity. While brief, it fails to be effectively concise due to the disjointed content.

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

Completeness2/5

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

Given the complexity (3 parameters, 0% schema coverage, no annotations, no output schema), the description is inadequate. It does not explain the parameters, the detection output, or the relationship between detection and the URL task. For a tool with no structured support, this leaves too many gaps.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It provides no information about what 'type', 'text', or 'detectionTypeList' mean, their expected formats, or how they influence detection. The description adds zero semantic value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'detects whether the text is AI-generated', which provides a clear purpose. However, it then confusingly adds instructions about extracting a taskId and constructing a URL, which seems unrelated to the core detection function. The purpose is somewhat vague due to this mixed messaging.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, constraints, or appropriate contexts for invocation. With no sibling tools, this is less critical but still a gap in usage instructions.

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/chongzixuan-ai/humanizer-mcp-server'

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