Skip to main content
Glama
appliedrelevance

Frappe MCP Server

by appliedrelevance
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

version

Retrieve the current version details of the Frappe MCP Server to verify compatibility and access capabilities.

Instructions

Get version information for the Frappe MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/tools/helpers.py:22-25 (handler)
    The handler function for the 'version' MCP tool. It returns a string with the Frappe MCP Server version information.
    @mcp.tool()
def version() -> str:
    """Get version information for the Frappe MCP server."""
    return f"Frappe MCP Server version {__version__}"
  • src/server.py:38-42 (registration)
    Registration block in the MCP server creation where the helpers module (containing the 'version' tool) is registered via helpers.register_tools(mcp).
    # Register all tool modules
helpers.register_tools(mcp)
documents.register_tools(mcp)
schema.register_tools(mcp)
reports.register_tools(mcp)
  • src/tools/helpers.py:14-30 (registration)
    The register_tools function in helpers.py that defines and registers the 'version' tool (along with ping and validate_auth) using @mcp.tool() decorators.
    def register_tools(mcp: Any) -> None:
    """Register helper tools with the MCP server."""
    
    @mcp.tool()
    def ping() -> str:
        """A simple tool to check if the server is responding."""
        return "pong"
    
    @mcp.tool()
    def version() -> str:
        """Get version information for the Frappe MCP server."""
        return f"Frappe MCP Server version {__version__}"
    
    @mcp.tool()
    def validate_auth() -> Dict[str, Any]:
        """Validate API credentials and return authentication status."""
        return validate_api_credentials()

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get'), which is straightforward, but doesn't add details like authentication requirements, rate limits, or what specific version information is returned. It's minimal but not misleading, fitting a baseline for a simple tool.

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, clear sentence that directly states the tool's function without any fluff or unnecessary elaboration. It's front-loaded and perfectly sized for its purpose, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is complete enough for basic understanding. It covers the core action and resource, and the output schema will handle return values, so gaps are minimal. However, it could benefit from slight elaboration on usage context to be fully comprehensive.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage, so there's no need for parameter details in the description. The description appropriately focuses on the tool's purpose without redundant information, earning a high score for efficiency in this context.

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 clearly states the action ('Get') and resource ('version information for the Frappe MCP server'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ping' or 'get_frappe_usage_info', which might also provide server-related information, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on the name alone. This lack of explicit guidance reduces its effectiveness in tool selection.

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/appliedrelevance/frappe-mcp-server'

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