Skip to main content
Glama
hsiangjenli

mcp-polib

by hsiangjenli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_poB

Return every entry from the requested PO file.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • entries: List of entries parsed from the PO file.

    • Example:

{
  "entries": [
    "unknown_type"
  ]
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}
write_poA

Create or update entries in a PO file and format it with powrap.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • success: Whether the write operation was successful.

      • message: Status message.

    • Example:

{
  "success": true,
  "message": "string"
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}
read_po_contextA

Return the target entry plus its surrounding context window.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • target_entry: The requested entry.

      • context_before: Entries preceding the target.

      • context_after: Entries succeeding the target.

    • Example:

{
  "target_entry": "unknown_type",
  "context_before": [
    "unknown_type"
  ],
  "context_after": [
    "unknown_type"
  ]
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}
find_fuzzyB

List every entry flagged as fuzzy in the provided PO file.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • entries: List of fuzzy entries found in the PO file.

    • Example:

{
  "entries": [
    "unknown_type"
  ]
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct, clearly described purpose: read all entries, write entries, read a specific entry with context, and list fuzzy entries. There is no meaningful overlap that would cause an agent to select the wrong tool.

Naming Consistency3/5

read_po and write_po follow a consistent verb_noun pattern, but read_po_context adds a qualifier and find_fuzzy drops the resource noun entirely. The names are readable but the convention is not uniformly applied.

Tool Count5/5

With 4 tools, the server is well-scoped for a focused PO file utility. Each tool covers a meaningful operation and none feel redundant or unnecessary.

Completeness4/5

The server covers the core read/write workflow plus useful context and fuzzy-entry queries for PO file management. It lacks an explicit delete operation, but this is a minor gap that can often be worked around via update operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources