Skip to main content
Glama

hive__solve

Run a hive job in one call: hire solvers, enforce cross-review, synthesize only reviewed solutions, settle escrow exactly-once, and return a content-addressed audit hash.

Instructions

[hive — auditable multi-solver orchestration over shared settlement rails] 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
depthNo
fee_bpsNo
problemYes
subtasksNo
redundancyNo
request_idNo
covenant_idNo
payment_refNo
budget_minorYes
accept_thresholdNo
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: forces reviewer!=author, synthesizes only reviewed content, settles escrows exactly-once, returns audit hash and telemetry, and pricing details. This provides rich context for decision-making.

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

Conciseness4/5

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

The description is concise (two sentences) and front-loads the core action. However, it uses jargon that may reduce clarity for some agents, and the density of information could be better structured with bullet points.

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

Completeness2/5

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

Given the tool's complexity (11 params, no output schema, no annotations), the description lacks essential detail: no parameter explanations, vague return description (audit hash and telemetry), and no mention of error conditions or prerequisites. The description is insufficient for a complex orchestration tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no explanation for any of the 11 parameters (e.g., problem, budget_minor, subtasks). The required parameters are not defined, leaving the agent without guidance on how to fill them correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool opens and runs a hive job, hires solvers, forces cross-review, synthesizes only reviewed content, settles escrows, and returns audit hash and telemetry. It distinguishes itself from sibling hive tools (e.g., hive__job_status, hive__audit_job) by being the main solve action.

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?

The description implies usage by explaining the orchestration process and mentions pricing (3 free/day, then $5). However, it does not explicitly state when not to use it or compare to alternatives like hive__audit_job, leaving the agent to infer the appropriate context.

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

Install Server

Other Tools

Latest Blog Posts

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/jdhart81/viridis-agent-fleet'

If you have feedback or need assistance with the MCP directory API, please join our Discord server