Skip to main content
Glama
CSOAI-ORG

Encoder AI MCP

Official

encode_html

Encode special characters into HTML entities to prevent injection attacks and ensure safe rendering in web pages.

Instructions

HTML-encode special characters.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: text (str): The text to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses read-only, stateless, idempotent behavior and rate limits, which adds value beyond missing annotations. However, the behavior description is generic and not tailored to HTML encoding, and includes incorrect details about 'structured analysis' that actually contradict the tool's function.

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 excessively long with redundant sections (e.g., behavioral transparency repeated under both 'Behavior' and 'Behavioral Transparency'). It includes irrelevant content about analysis/classification, making it poorly structured and not concise.

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?

Despite having an output schema, the description lacks any mention of return values or output format. It omits tool-specific details like which characters are encoded or examples. The generic analysis content makes it incomplete for the actual encoding tool.

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

Parameters2/5

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

With 0% schema description coverage, the description should explain the parameters but only gives vague phrases: 'text: The text to analyze or process' and 'api_key: The api key to analyze or process'. It fails to indicate that 'text' is a string to be HTML-encoded and that 'api_key' is optional.

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 first sentence clearly states 'HTML-encode special characters', but the subsequent description talks about 'structured analysis or classification' which is unrelated and confusing. The purpose is partially clear but undermined by conflicting content.

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?

Provides generic when-to-use and when-not-to-use guidelines that describe 'analysis or classification' rather than HTML encoding. This misleads the agent about appropriate use cases and fails to differentiate from sibling tools like encode_base64 or encode_url.

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/CSOAI-ORG/encoder-ai-mcp'

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