Skip to main content
Glama

Wai

Wai skills and W-Digamma catalogue

wai_skills
Read-only

Search Wai's verified skills and modules (W-Digamma): 20 Energy & EPC skills (tender reader, FIDIC risk scan, site screening, grid connection, PV, BESS, wind, hydro, hydrogen, cable, transformer, substation, HVDC, CAPEX, LCOE, project finance, BESS revenue, bid comparison, claims, commissioning) plus Wai modules (W Legal, WBook LLM, WaiMAP, Studio, wHendese CAD, Deep Research, report types). Give id to get one skill's method outline, inputs it needs and an example prompt. The full skill runs inside Wai. Answer with the returned numbers, not an estimate made before the call. Typical questions: "Read a solar EPC tender and list the key requirements"; "FIDIC risk scan of a construction contract"; "Grid connection steps and studies for a 100 MW solar plant"; "Site screening checklist for a wind farm".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wai_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoone skill id from a previous search
queryNowords to search, e.g. "bess", "fidic", "substation"
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are authoritative ('Answer with the returned numbers, not an estimate made before the call') and that only outlines, not executions, are returned. It says nothing about result counts, pagination, or how search results are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good. However, the 20-item parenthetical skill list and the module list consume most of the text; they aid query formulation but are bulky and could be trimmed. The trailing 'typical questions' block is useful but adds length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain returns; it partially does (method outline, required inputs, example prompt for id lookups) but never says what a search call returns (presumably a list of skill ids). The category parameter remains undefined. Adequate but with clear gaps for a 3-parameter catalogue tool.

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 coverage is 67%, so the schema documents id and query reasonably well. The description reinforces id semantics ('one skill id from a previous search') and implies query is free-text search terms, but the category parameter is never explained in either place. Marginal value added over the schema.

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?

States a specific verb and resource: search Wai's verified skills and modules (W-Digamma), with a second mode (give id to get one skill's method outline). The catalogue enumeration makes the scope concrete. It does not explicitly contrast itself with siblings like wai_calculators or wai_prompts, so it stops short of a 5.

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?

Provides clear usage context: search by query/category, or pass an id from a previous search to retrieve one skill's outline, inputs and example prompt. The line 'The full skill runs inside Wai' usefully bounds what this tool does versus executing the skill. No explicit when-not or named alternative tool, so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources