agent-hive-orchestrator
Server Details
Deterministic nested hive-mind orchestration over the A2A rails: hire N solvers, adversarial cross-r
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jdhart81/viridis-agent-fleet
- GitHub Stars
- 0
- Server Listing
- viridis-agent-fleet
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolsaudit_jobInspect
Return the full content-addressed lineage of a completed job: plan, hires (including refused ones with reasons), contributions, reviews, settlements, rail calls (with simulated flags), and synthesis.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
describe_agentInspect
Return fleet-standard capabilities, actions, invariants, and pricing.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
job_statusInspect
Return job state, plan hash, and live budget conservation books.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_solversInspect
List the registered solver pool: id, kind (worker|hive), price, capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
solveAInspect
Open and run a hive job in one call: hire solvers through the rails (covenant -> escrow -> meter), force reviewer!=author cross-review, synthesize only what survives review, settle every escrow exactly-once, and return a content-addressed audit hash plus bits-per-joule telemetry. Price: $5.00 per solve after 3 free/day; sub-hires settle via escrow at each solver's list price.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | ||
| depth | No | ||
| fee_bps | No | ||
| problem | Yes | ||
| subtasks | No | ||
| redundancy | No | ||
| request_id | No | ||
| covenant_id | No | ||
| payment_ref | No | ||
| budget_minor | Yes | ||
| accept_threshold | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Given no annotations, the description carries the full burden and details several behavioral traits: hiring solvers via covenant-escrow-meter pipeline, forced cross-review, synthesis of survivors, exactly-once settlement, and return of audit hash and telemetry. It does not cover failure modes or rate limits, but the provided detail is substantial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, information-dense paragraph that front-loads the main purpose. It is fairly concise given the complexity, though some procedural details (e.g., exact steps) could be streamlined.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite an output schema existing and complexity (11 parameters), the description does not explain parameter semantics or output structure beyond mentioning audit hash and telemetry. It is insufficient for an agent to correctly configure the tool without additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage and 11 parameters, the description adds minimal parameter semantics. It mentions pricing context but does not explain any parameter's meaning, usage, or format, leaving the agent to rely solely on schema titles.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Open and run a hive job in one call', identifying the specific verb and resource. It distinguishes from sibling tools like 'audit_job' (post-hoc auditing) and 'job_status' (status checking) by emphasizing the combined submission and execution workflow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context on when to use this tool (for submitting and running a hive job in one call) and includes pricing information. However, it does not explicitly exclude alternatives or state when not to use it, missing some guidance for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
verify_auditInspect
Recompute the audit digest from a presented lineage (never trusts the embedded hash) and report whether it matches a job this hive ran.
| Name | Required | Description | Default |
|---|---|---|---|
| audit_json | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.