fiberone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIBERONE_TOKEN | No | Pre-obtained bearer token to skip login entirely (optional if username/password provided) | |
| FIBERONE_PASSWORD | No | Your portal login password | |
| FIBERONE_USERNAME | No | Your portal login username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Log in to the FiberOne API. Uses FIBERONE_USERNAME/FIBERONE_PASSWORD env by default; pass explicit credentials to override. |
| logoutA | End the session on the FiberOne API and clear the cached token. |
| get_accountA | Get the logged-in subscriber's account details. |
| get_dashboardB | Get dashboard overview stats for the current subscriber. |
| get_usageC | Get data usage for the subscriber. |
| get_transactionsB | List payment transactions (most recent first). |
| get_plansB | List available plans/packages. |
| get_outage_ticketsB | List outage tickets for the account. |
| create_outage_ticketA | Create a new support ticket. This is an action tool: it files a real report with FiberOne. |
| get_modem_infoA | Get modem/router devices on the account. |
| get_ticket_categoriesA | List support ticket categories and priorities. |
| get_lost_daysB | List lost days (downtime compensation credits) for the account. |
| get_usage_historyA | Get historical data usage (daily download/upload series). |
| get_pause_statusA | Check account pause eligibility: days paused, days left this year, pause reasons. |
| get_pause_historyA | List past account pauses. |
| get_autorenew_statusA | Get auto-renew status: agreed, saved card, opt-out state. |
| get_pay4me_historyA | List pay-for-me requests (someone else paying for this account). |
| get_renewal_planA | Get the plan details used for renewal (price, validity, speed). |
| get_upgrade_plansA | List plans the account can upgrade to. |
| get_experience_centresA | List FiberOne physical experience centres (address, city). |
| get_faqsA | List FiberOne FAQs. |
| get_ticketA | Get one support ticket with its message thread. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Tool names clearly indicate distinct resources: account, usage, transactions, tickets, modem, pause, autorenew, plans, etc. A few related plan tools (get_plans, get_renewal_plan, get_upgrade_plans) could be confused, but descriptions clarify their scope.
The set consistently uses lowercase snake_case, with get_ as the dominant read prefix and action verbs for the few writes (login, logout, create_outage_ticket). login/logout break the verb_noun pattern slightly, but the convention is predictable.
At 22 tools, the server is on the heavy side and includes several peripheral getters (FAQs, experience centres, dashboard) that could be trimmed. The count is not unreasonable for a broad ISP self-service API, but it exceeds the ideal 3-15 range.
The surface is heavily read-only: it exposes status and history for pauses, auto-renew, pay4me, and upgrades, but no corresponding actions to pause, update auto-renew, create a pay4me request, or upgrade. With only create_outage_ticket as a mutating tool, agents will hit dead ends on common account-management tasks.