Skip to main content
Glama
Sign In

HumanLeg.ai

by io.github.humanleg-ai
OverviewDiscussionsAdmin

Create HumanLeg fee quote

humanleg_create_fee_quote

Create a short-lived synthetic fee quote before creating a task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rewardUsdc": "<rewardUsdc>",
      "displayAud": "<displayAud>"
    },
    "name": "humanleg_create_fee_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
displayAudYesHuman-readable AUD equivalent.
rewardUsdcYesWorker reward in synthetic USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Short-lived" hints at expiry and "synthetic" hints that no real money moves, which is useful, but there is nothing about permissions, whether calling it has side effects, how long the quote lasts, or what the response contains. For a mutation-adjacent creation tool this leaves significant gaps.

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?

A single front-loaded sentence with no redundant wording. It is efficient, though its brevity borders on under-specification rather than tight editing.

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?

With no annotations, no output schema, and a quote lifecycle that the agent must understand to sequence calls correctly, the description should say more: quote validity window, whether the quote ID is returned, and how it is passed to humanleg_create_task. As written, an agent knows the ordering but not the mechanics.

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 description coverage is 100%, and the schema documents both rewardUsdc and displayAud, so the baseline is 3. The description adds no meaning about how the two amounts relate (e.g., whether displayAud must be consistent with rewardUsdc) or about the 20 USDC minimum.

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

Purpose4/5

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

States a specific verb and resource ("Create ... fee quote") and names the entity it relates to ("task"), so it is distinguishable from the sibling humanleg_create_task. It does not explicitly say how it differs from the other get_* siblings, but the noun phrase does most of the work.

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

Usage Guidelines3/5

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

The phrase "before creating a task" implies sequencing: obtain a quote first, then create the task. However, it gives no exclusions (when not to call it), no statement about whether a quote is mandatory, and no guidance on what to do with the quote once obtained.

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

All HumanLeg.ai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources