Skip to main content
Glama

Hydracept

by com.hydracept
OverviewDiscussionsAdmin

Run a capability

hydracept_run

Run a capability (paid). Use when the user wants execution — not for quotes (hydracept_quote_capability), status (hydracept_job_status), or receipts (hydracept_get_receipt). Default wait=true waits until the job finishes; use hydracept_submit_job when this call must return immediately. Picks invoke vs durable job from the capability descriptor. Requires bearer key. Settles at actual provider cost plus any managed service fee; no per-call minimum. May create jobs, artifacts, and provider usage. Returns: Terminal hydracept.run-result.v1 or job envelope when wait=false. Errors: WORKSPACE_KEY_REQUIRED, INVALID_ARGUMENT, FundingRequired, EXECUTION_FAILED, job timeout when wait exhausts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequired capability input object (schema fields). Merged with session project context when bound.
waitNoBoolean, default true. When true, poll until succeeded/failed/canceled or timeout. When false, return job id and poll with hydracept_job_status.
inputNoAlias for body; do not pass both.
timeoutNoSeconds to poll when wait=true; omit to poll until terminal with no tool-side limit (the MCP client request timeout may end the call first). On timeout, status may stay running — call hydracept_job_status.
max_costNoOptional number (USD): sets execution.executionConstraints.maxCostUsd before submit.
capability_keyYesRequired capability registry key for POST .../jobs.
idempotency_keyNoOptional string; server generates run-{uuid} when empty. Reuse for safe retries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"Required capability input object (schema fields). Merged with session project context when bound."
    • addedInput schema / properties / capability_key / description
      Added value: +"Required capability registry key for POST .../jobs."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Optional string; server generates run-{uuid} when empty. Reuse for safe retries."
    • addedInput schema / properties / input / description
      Added value: +"Alias for body; do not pass both."
    • addedInput schema / properties / max_cost / description
      Added value: +"Optional number (USD): sets execution.executionConstraints.maxCostUsd before submit."
    • addedInput schema / properties / timeout / description
      Added value: +"Seconds to poll when wait=true; omit to poll until terminal with no tool-side limit (the MCP client request timeout may end the call first). On timeout, status may stay running — call hydracept_job_status."
    • addedInput schema / properties / wait / description
      Added value: +"Boolean, default true. When true, poll until succeeded/failed/canceled or timeout. When false, return job id and poll with hydracept_job_status."
  2. Changed7 schema fields changed
    • removedInput schema / properties / body / description
      Removed value: -"Required capability input object (schema fields). Merged with session project context when bound."
    • removedInput schema / properties / capability_key / description
      Removed value: -"Required capability registry key for POST .../jobs."
    • removedInput schema / properties / idempotency_key / description
      Removed value: -"Optional string; server generates run-{uuid} when empty. Reuse for safe retries."
    • removedInput schema / properties / input / description
      Removed value: -"Alias for body; do not pass both."
    • removedInput schema / properties / max_cost / description
      Removed value: -"Optional number (USD): sets execution.executionConstraints.maxCostUsd before submit."
    • removedInput schema / properties / timeout / description
      Removed value: -"Seconds to poll when wait=true; omit to poll until terminal with no tool-side limit (the MCP client request timeout may end the call first). On timeout, status may stay running — call hydracept_job_status."
    • removedInput schema / properties / wait / description
      Removed value: -"Boolean, default true. When true, poll until succeeded/failed/canceled or timeout. When false, return job id and poll with hydracept_job_status."
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"Required capability input object (schema fields). Merged with session project context when bound."
    • addedInput schema / properties / capability_key / description
      Added value: +"Required capability registry key for POST .../jobs."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Optional string; server generates run-{uuid} when empty. Reuse for safe retries."
    • addedInput schema / properties / input / description
      Added value: +"Alias for body; do not pass both."
    • addedInput schema / properties / max_cost / description
      Added value: +"Optional number (USD): sets execution.executionConstraints.maxCostUsd before submit."
    • addedInput schema / properties / timeout / description
      Added value: +"Seconds to poll when wait=true; omit to poll until terminal with no tool-side limit (the MCP client request timeout may end the call first). On timeout, status may stay running — call hydracept_job_status."
    • addedInput schema / properties / wait / description
      Added value: +"Boolean, default true. When true, poll until succeeded/failed/canceled or timeout. When false, return job id and poll with hydracept_job_status."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing payment settlement model (actual provider cost + fee, no minimum), auth requirement (bearer key), side effects (creates jobs, artifacts, provider usage), wait semantics, and enumerated error codes. Annotations only give the mutation safety profile; the description carries the real behavioral weight.

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?

Dense but well organized: routing first, then wait semantics, then cost/auth, then returns and errors. Every sentence earns its place, though the error-code list is compact and slightly terse.

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

Completeness5/5

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

Given an output schema exists, the description still names return shapes, side effects, auth, cost, and failure modes, leaving nothing an agent needs before calling. Complete for a paid, side-effecting execution 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 100%, so parameters are already documented. The description reinforces wait=true default and the invoke-vs-durable-job selection but adds little parameter detail beyond schema; baseline 3 is appropriate.

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?

States a specific verb and resource ('Run a capability') and immediately distinguishes itself from siblings hydracept_quote_capability, hydracept_job_status, and hydracept_get_receipt via explicit 'not for' clauses. An agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names when to use (execution) and when not to (quotes, status, receipts), and routes the immediate-return case to hydracept_submit_job. Alternatives and their selecting conditions are all stated.

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

All Hydracept toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources