Skip to main content
Glama
gowinston-ai

winston-ai-mcp

Official
by gowinston-ai

AI Text Detection

ai-text-detection
Read-only

Analyze text, files, or websites to determine the likelihood of AI authorship. Scans up to 150,000 characters per request.

Instructions

Detects AI content in a given text to detect the likelihood of the text being written by an AI. Cost: 1 credit per word.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to scan. Texts under 600 characters may produce unreliable results and should be avoided. Maximum 150 000 characters per request.
fileNoA file to scan. If you supply a file, the API will scan the content of the file. The file must be in plain .pdf, .doc or .docx format. The file has priority over the text, so if you give a text and a file, it's the file that will be scanned.
websiteNoA website URL to scan. If you supply a website, the API will fetch the content of the website and scan it. The website must be publicly accessible. It's important to know that the website has priority over the text and the file, so if you give a text, a file and a website, it's the website that will be scanned.
Behavior4/5

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

The description adds cost per word (1 credit per word) beyond the annotations (readOnlyHint, openWorldHint). While annotations already cover safety, the cost is a behavioral trait. However, it does not discuss reliability thresholds or output format.

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

Conciseness4/5

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

The description is concise (one sentence plus cost info) and front-loaded. The only minor waste is repetition of 'detect'. It is efficient but could be slightly more structured.

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?

The description lacks return value details (e.g., score or percentage). With no output schema, the agent cannot infer what the tool returns. Also, the priority order among text/file/website is described in the schema but not in the description, which could be helpful. The cost is mentioned, but completeness is insufficient.

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 description coverage is 100% (all parameters have descriptions). The tool description adds no further meaning beyond the schema; the cost note applies to the tool overall, not specific parameters. Baseline score of 3 is appropriate.

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 explicitly states the tool's purpose: 'Detects AI content in a given text to detect the likelihood of the text being written by an AI.' It clearly distinguishes from siblings like ai-image-detection (image focus) and plagiarism-detection (plagiarism focus).

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 implies usage for text-based AI detection and mentions cost, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like plagiarism-detection. No exclusions or selection criteria are given.

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/gowinston-ai/winston-ai-mcp-server'

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