Skip to main content
Glama
wrecks1997

Koha MCP Server

by wrecks1997
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    The two tools have completely distinct purposes: search_books retrieves bibliographic records, while check_availability checks item status. There is no overlap, making tool selection unambiguous.

    Naming Consistency5/5

    Both tool names follow the same verb_noun snake_case pattern: search_books and check_availability. The naming is consistent and intuitively indicates each tool's action and target.

    Tool Count3/5

    With only 2 tools, the set feels thin but is appropriate for a narrowly scoped discovery and availability-checking service. It is not excessive, but the small number limits the server's overall utility.

    Completeness4/5

    The search-then-check-availability workflow is fully covered with no dead ends. A minor gap is the absence of a direct fetch-by-ID tool for full bibliographic details, but the search results likely provide sufficient information for the core use case.

  • Average 4.2/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    Annotations already declare readOnlyHint=true, and the description adds useful context beyond that: it returns item-level details including call number, location, and the circulation status of each copy. It does not contradict the annotations and provides a clear picture of what the read operation yields.

    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?

    The description is a single, dense sentence that front-loads the purpose and immediately provides the key return summary. Every word earns its place, with no redundant or filler content.

    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 one-parameter read-only tool, the description adequately covers purpose and return content (item-level call number, location, availability/checkout status). Although there is no output schema and error behavior is not mentioned, the description provides enough for an agent to invoke the tool correctly in typical use.

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

    Parameters3/5

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

    Schema description coverage is 100% for the single parameter, and the schema already explains that biblio_id comes from search_books results. The tool description only restates 'specific book' and adds no extra parameter semantics, so the schema carries the burden.

    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?

    The description uses a specific verb ('check') and resource ('a specific book by its biblio_id'), clearly stating the tool's scope. It also lists the return details (call number, location, availability), which distinguishes it from the sibling search_books that finds books rather than checking availability.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines4/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description implies usage after obtaining a biblio_id from search_books, especially through the parameter description ('The biblio_id from search_books results'). However, it does not explicitly state when to use this tool versus search_books or mention alternative/exclusion scenarios, so it stops short of a 5.

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

  • Behavior4/5

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

    With readOnlyHint annotation already signaling a safe read operation, the description adds value by disclosing that the tool returns matching books with biblio_id, which is not in the schema. It also connects to check_availability, though it doesn't mention rate limits or error behavior; for a simple read-only search, this is adequate.

    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?

    The description is a single, well-structured sentence that front-loads the main action, then explains the output and downstream usage. It contains no superfluous words and is well-organized.

    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 read-only search tool with three parameters and a sibling, the description covers the essential purpose, output (biblio_id), and relationship to check_availability. It does not specify defaults for limit or search_type, but those are fully documented in the schema, so no critical information is missing.

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

    Parameters3/5

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

    All three parameters (query, limit, search_type) have complete schema descriptions, so the high-coverage baseline applies. The description restates the search types but adds no supplementary syntax, examples, or parameter-specific behavior 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?

    The description uses a specific verb 'Search' targeting the GBS library catalog, enumerates search dimensions (title, author, ISBN, subject, or keyword), and explains the output (biblio_id) for use with check_availability. This clearly distinguishes its role from the sibling tool.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines4/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description implies a clear workflow by stating 'for use with check_availability', indicating that this tool is a precursor for availability checks. It lacks explicit when-not-to-use instructions but provides enough contextual guidance for an agent to understand when this tool is appropriate.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

koha-mcp-server MCP server

Copy to your README.md:

Score Badge

koha-mcp-server MCP server

Copy to your README.md:

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/wrecks1997/koha-mcp-server'

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