Skip to main content
Glama
JayOfemi

Byakugan: Private, open-source AI-text checker

Find AI tells

find_ai_tells

Locate exact character spans that read as AI-written, including stock phrasing, long dashes, and formulaic openers. Rephrase only the flagged parts to preserve your writing.

Instructions

Locate the exact character spans that read as AI, covering stock phrasing, long dashes, and formulaic sentence openers. Returns a list of spans with start, end, the matched text, and a note. Use these to rephrase only the flagged parts and leave the rest of the writing intact. Deterministic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to analyze.
Behavior4/5

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

No annotations provided, so the description carries full burden. It declares the tool as deterministic and describes the return format (list of spans with start, end, matched text, note). This discloses key behavioral traits.

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?

Three sentences, front-loaded with main action, no wasted words. Every sentence adds value.

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?

For a simple tool with one parameter, no output schema, and no annotations, the description covers purpose, return structure, and usage hint. It lacks details like indexing but is sufficient.

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 coverage is 100% with parameter description 'The text to analyze.' The description adds context about analyzing text for AI tells but does not add new semantic details beyond the schema.

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 verb (locate), resource (character spans that read as AI), and provides specific examples (stock phrasing, long dashes, formulaic sentence openers). It distinguishes from siblings: check_grammar, check_reuse, detect_ai_text, by focusing on exact spans for AI tells.

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 advises using results to rephrase only flagged parts, indicating when to use (targeted rephrasing). It does not explicitly state when not to use or compare to siblings, but the intent is clear.

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/JayOfemi/byakugan'

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