Skip to main content
Glama
Sign In
TextToolkit

TextToolkit

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

encode_html

Convert plain text into HTML entities to prevent rendering issues and ensure safe display in web pages.

Instructions

Encode HTML entities

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "encode_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to encode or decode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior1/5

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

The main description only says 'Encode HTML entities', but the input schema parameter description says 'The text to encode or decode', creating a contradiction about whether the tool also decodes. With no annotations, this inconsistency undermines behavioral transparency.

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 extremely concise at three words, front-loading the core purpose. However, it is too brief and could benefit from a sentence clarifying the operation, especially given the parameter confusion.

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?

For a simple 1-parameter tool with no output schema, the description is insufficient. It fails to resolve the encode/decode ambiguity or specify behavior like which entities are encoded, leaving the agent with incomplete information.

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?

The input schema covers 100% of parameters, so a baseline of 3 applies. However, the parameter description 'encode or decode' contradicts the tool purpose, adding confusion instead of clarity. The description adds no meaningful semantic value beyond the schema.

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 'Encode HTML entities' clearly states the action (encode) and resource (HTML entities), distinguishing it from siblings like decode_html. However, it is slightly generic and could specify the exact transformation (e.g., escaping special characters).

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 on when to use this tool versus alternatives like encode_url or decode_html. The description does not mention prerequisites or exclusions, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools