Skip to main content
Glama
scotia1973-bot

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

mask_text

Mask sensitive text such as email, credit card numbers, or phone numbers by replacing middle characters while keeping the start and end visible for readability.

Instructions

Mask parts of sensitive text while keeping ends visible.

Parameters:
    text — Text to mask (e.g. email, credit card, phone).
    mask_char — Character for masking (default: '*').
    visible_start — Characters to leave visible at start (default: 1).
    visible_end — Characters to leave visible at end (default: 1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
mask_charNo*
visible_startNo
visible_endNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

No annotations are provided, so description carries full burden. It discloses the masking behavior and keeps ends visible. It does not cover edge cases like very short text, but for a simple transformation, it is adequately transparent.

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?

Description is concise with a clear purpose statement followed by a bullet list of parameters. No superfluous information; 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 4 parameters and an output schema, the description covers input semantics well. It does not describe the return value, but the output schema exists to cover that. Could be slightly more complete by mentioning that output is a masked string.

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

Parameters5/5

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

Schema description coverage is 0%, but the description lists all parameters with explanations (e.g., 'text — Text to mask (e.g. email, credit card, phone)') and defaults. This compensates fully, adding meaning 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?

Description clearly states 'Mask parts of sensitive text while keeping ends visible.' It uses a specific verb-resource pair and distinguishes from siblings by specifying the masking behavior and examples of text types (email, credit card, phone).

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?

Description implies usage by giving examples (email, credit card, phone) but does not explicitly state when to use this tool over alternatives or when not to use it. No guidance on selection among siblings.

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/scotia1973-bot/api-hub'

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