Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use Model Context Protocol servers to access external tools and data sources. Enable AI agents to discover and execute tools from configured MCP servers (legal databases, APIs, database connectors, weather services, etc.).
Use Model Context Protocol servers to access external tools and data sources. Enable AI agents to discover and execute tools from configured MCP servers (legal databases, APIs, database connectors, weather services, etc.).
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use the MCP integration plugin to discover and execute tools provided by external MCP servers. This skill enables you to access legal databases, query APIs, search databases, and integrate with any service that provides an MCP interface. The plugin provides a unified mcp tool with two actions: list - Discover available tools from all connected servers call - Execute a specific tool with parameters
Always start by listing available tools to see what MCP servers are connected and what capabilities they provide. Action: { tool: "mcp", args: { action: "list" } } Response structure: [ { "id": "server:toolname", "server": "server-name", "name": "tool-name", "description": "What this tool does", "inputSchema": { "type": "object", "properties": {...}, "required": [...] } } ]
For each tool, examine: id: Format is "server:toolname" - split on : to get server and tool names description: Understand what the tool does inputSchema: JSON Schema defining parameters properties: Available parameters with types and descriptions required: Array of mandatory parameter names
Common tool naming patterns: search_* - Find or search operations (e.g., search_statute, search_users) get_* - Retrieve specific data (e.g., get_statute_full_text, get_weather) query - Execute queries (e.g., database:query) analyze_* - Analysis operations (e.g., analyze_law) resolve_* - Resolve references (e.g., resolve_citation)
Before calling a tool: Identify all required parameters from inputSchema.required Verify parameter types match schema (string, number, boolean, array, object) Check for constraints (minimum, maximum, enum values, patterns) Ensure you have necessary information from the user
Action: { tool: "mcp", args: { action: "call", server: "<server-name>", tool: "<tool-name>", args: { // Tool-specific parameters from inputSchema } } } Example - Korean legal search: { tool: "mcp", args: { action: "call", server: "kr-legal", tool: "search_statute", args: { query: "μ°μ₯κ·Όλ‘ μλΉ", limit: 5 } } }
Tool responses follow this structure: { "content": [ { "type": "text", "text": "JSON string or text result" } ], "isError": false } For JSON responses: const data = JSON.parse(response.content[0].text); // Access data.result, data.results, or direct properties
For complex requests, execute multiple tools in sequence: Example - Legal research workflow: Search - search_statute to find relevant laws Retrieve - get_statute_full_text for complete text Analyze - analyze_law for interpretation Precedents - search_case_law for related cases Each step uses output from the previous step to inform the next call.
Between tool calls: Extract relevant information from each response Use extracted data as parameters for subsequent calls Build up understanding progressively Present synthesized results to user
"Tool not found: server:toolname" Cause: Server not connected or tool doesn't exist Solution: Run action: "list" to verify available tools Check spelling of server and tool names "Invalid arguments for tool" Cause: Missing required parameter or wrong type Solution: Review inputSchema from list response Ensure all required parameters provided with correct types "Server connection failed" Cause: MCP server not running or unreachable Solution: Inform user service is temporarily unavailable Suggest alternatives if possible
Errors return: { "content": [{"type": "text", "text": "Error: message"}], "isError": true } Handle gracefully: Explain what went wrong clearly Don't expose technical implementation details Suggest next steps or alternatives Don't retry excessively
{tool: "mcp", args: {action: "list"}} Response shows kr-legal:search_statute with: Required: query (string) Optional: limit (number), category (string)
{ tool: "mcp", args: { action: "call", server: "kr-legal", tool: "search_statute", args: { query: "μ°μ₯κ·Όλ‘ μλΉ", category: "λ Έλλ²", limit: 5 } } }
const data = JSON.parse(response.content[0].text); // Present data.results to user User-facing response: Found 5 Korean statutes about overtime pay: 1. κ·Όλ‘κΈ°μ€λ² μ 56μ‘° (μ°μ₯Β·μΌκ° λ° ν΄μΌ κ·Όλ‘) - Overtime work requires 50% premium 2. κ·Όλ‘κΈ°μ€λ² μ 50μ‘° (κ·Όλ‘μκ°) - Standard working hours: 40 hours per week Would you like me to retrieve the full text of any statute?
{tool: "mcp", args: {action: "list"}}
{ tool: "mcp", args: { action: "call", server: "server-name", tool: "tool-name", args: {param1: "value1"} } }
Tool ID parsing: "server:toolname" β split on : for server and tool names Parameter validation: Check inputSchema.required and inputSchema.properties[param].type Response parsing: JSON.parse(response.content[0].text) for JSON responses Error detection: Check response.isError === true
Plugin README: README.md - Installation and configuration Real Example: REAL_EXAMPLE_KR_LEGAL.md - Working kr-legal setup API Reference: API.md - Technical API details Configuration: CONFIGURATION.md - Server configuration guide Troubleshooting: TROUBLESHOOTING.md - Common issues and solutions
Examples Collection: EXAMPLES.md - 13 real-world examples including: Legal research workflows Database queries Weather service integration Multi-step complex workflows Error handling patterns Remember: Always start with action: "list" when uncertain about available tools.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.