OpenMesha
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_agentsA | List in-process agent records (id, status, spend, budget, capabilities). Use before run_task to discover agent_id values. Read-only snapshot of this process. Does not create agents (create_agent) or start work (run_task). |
| create_agentA | Create an agent process with intent, USD budget, and capabilities. Returns agent_id for later run_task / list_agents. Does not execute a goal. Side effect: writes the in-memory process table. Default model is mock-gpt. |
| run_taskA | Run one goal on an existing agent until completion, policy deny, or budget stop. Blocks up to 120s. Missing agent_id returns an error object. Use create_agent first. Not for multi-agent orchestration (create_workflow). Side effects: task row + spend. |
| get_cost_ledgerA | Return the token/$ cost ledger for this process. Use to audit spend after run_task. Read-only. Not get_audit_log or get_metrics. |
| get_audit_logA | Return governance allow/deny records from AgentFence. Use after a blocked run_task. Read-only. Not the dollar ledger (get_cost_ledger). |
| get_metricsA | Return runtime counters (agents created, tasks). Use for health checks. Read-only. Does not include cost rows or policy events. |
| create_workflowA | Create specialist agents and run a sequential multi-agent workflow. Default roles are planner then worker, sharing budget_usd. Use when a goal needs more than one agent. Do not use to run a single existing agent (run_task). Side effects: creates agents + tasks and marks the workflow completed. |
| list_available_toolsA | List capability names that can be granted to agents. Use before create_agent to choose the capabilities argument. Read-only. |
| x402_payment_quoteA | Return an offline x402 payment quote for a named service. Read-only simulation. Does not charge or call a facilitator. Missing services return an error object. Not create_agent or run_task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct action or resource: agent lifecycle, workflow creation, reporting, capability listing, and payment quoting are clearly separated. The get_cost_ledger, get_audit_log, and get_metrics tools explicitly disambiguate their boundaries in their descriptions.
Most tools follow a clear verb_noun pattern such as list_agents, create_agent, run_task, and get_metrics. The outlier is x402_payment_quote, which is a noun-phrase name with no leading verb, creating a minor inconsistency.
Nine tools is a well-scoped count for an agent orchestration and governance server. Each tool addresses a meaningful part of the workflow without feeling redundant or padded.
The core lifecycle of creating agents, listing agents, running tasks, and creating workflows is covered, along with cost, audit, and metrics reporting. Missing update/delete/stop agent operations are notable but not critically blocking for the apparent in-process simulation scope.