Works With Agents MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wwa_facts_queryA | Query the shared agent knowledge base. Facts are structured environment truths — Python paths, project structures, preferences, deployment targets. Agents discover facts without re-asking users or searching blindly. |
| wwa_facts_list_categoriesA | List all available fact categories and their counts. Use this to discover what knowledge domains are available before querying specifics. |
| wwa_pitfalls_lookupA | Search known failure patterns and verified fixes. Each pitfall comes from real agent failures — not LLM hallucinations. Covers deployment, packaging, tooling, configuration. Before debugging something new, check here first — someone probably broke it already. |
| wwa_skills_searchA | Search the agent skill library for reusable workflows. Each skill is a battle-tested procedure with exact commands, known pitfalls, and verification steps. Before tackling a new task, search here — the procedure might already exist. |
| wwa_skills_list_categoriesA | List all available skill categories and their counts. Maps to directories under ~/.hermes/skills/. |
| wwa_handoff_createA | Create a structured agent-to-agent task handoff. When one agent must transfer an in-progress task to another, this ensures complete context transfer — no data loss, no silent drops, full attribution chain. Implements the Works With Agents Handoff Protocol v1.0.0-draft. |
| wwa_handoff_verifyA | Verify a handoff document before accepting it. Validates structure, required fields, and completeness. Catches incomplete transfers before work begins — preventing context loss between agents. |
| wwa_handoff_validate_schemaA | Full schema validation of a handoff document against the Handoff Protocol v1.0.0-draft. Stricter than verify — checks types, UUIDs, status values, and protocol compliance. |
| wwa_blueprint_searchC | Search the Works With Agents blueprint registry. Blueprints are CC BY 4.0 reference specifications for AI agent infrastructure — handoff protocols, trust scoring, compliance frameworks, deployment manifests, agent OSI model. Free to use, adapt, and implement. |
| wwa_blueprint_validateA | Validate an implementation against a blueprint specification. Check if your handoff, deployment manifest, or trust score implementation conforms to the spec. |
| wwa_trust_score_calculateA | Calculate an AI agent trust score using the Works With Agents Trust Score spec v1.0.0-draft. Weighs task success rate (30%), pitfall contributions (20%), skill quality/reuse (20%), peer rating (15%), and uptime (15%). Returns score, tier, autonomy level, and improvement recommendations. |
| wwa_identity_verifyA | Verify an agent's Ed25519 cryptographic signature. Proves that an agent with a given public key signed a specific message. Used for subagent output verification, capability attestation, and agent-to-agent authentication. Implements Works With Agents Identity Protocol v1.0.0-draft. |
| wwa_sla_validateA | Validate agent fleet metrics against SLA tier thresholds. Checks whether your agent fleet meets service level guarantees for best-effort, production, or regulated tiers. Implements Works With Agents SLA Framework v1.0.0-draft. |
| wwa_compliance_checkA | Validate an agent implementation against a Compliance-as-Code ruleset. Regulation-agnostic validation engine — supply any ruleset (DTAC, FCA, GDS, GDPR, SOC2, ISO 27001) and your implementation config. Implements Works With Agents Compliance-as-Code spec v1.0.0-draft. |
| wwa_devloop_setupA | Get the full Works With Agents SPFx Component Scaffolding (Dev-Loop) setup guide. Returns MCP server install instructions (pip install wwa-scaffold-mcp), available tools, dashboard features, and architecture. Agents discovering WWA infrastructure call this to learn about the scaffolding tool. |
| wwa_generate_keyA | Generate a new API key for accessing Works With Agents MCP tools. No authentication required — returns a key with 'free' tier. Use the returned key in subsequent calls via the 'x-api-key' argument. |
| wwa_tender_searchB | Search UK public-sector tender opportunities from Contracts Finder and Find a Tender. Returns combined, deduplicated results from both sources. Filter by keyword, value range, and status. |
| wwa_bid_indexA | Index a past bid or proposal into the bid content library. Stores content locally with full-text search. Use this to build a library of past responses for future drafting. |
| wwa_bid_searchA | Semantic search across the bid content library. Finds relevant past bids by matching against stored content. Returns snippets with relevance scores. |
| wwa_bid_listB | List all bids in the library with optional status or client filter. |
| wwa_bid_getA | Get the full content of a specific bid by its ID. Returns complete bid text, metadata, and sections. |
| wwa_bidmate_scoreA | Go/no-go scoring for a tender opportunity. Evaluates a tender against your bidder profile and returns a score (0-100), verdict, risks, and strengths. Can use AI analysis if API key provided. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/vystartasv/wwa-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server