Skip to main content
Glama
Sign In

HumanLeg.ai

by io.github.humanleg-ai
OverviewDiscussionsAdmin

Create and review HumanLeg task

humanleg_create_task

Create a bounded task and run compliance review. This does not fund or publish the 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": {
      "feeQuoteId": "<feeQuoteId>",
      "title": "<title>",
      "instructions": "<instructions>",
      "evidenceRequirements": "<evidenceRequirements>",
      "rewardUsdc": "<rewardUsdc>",
      "displayAud": "<displayAud>",
      "deadline": "<deadline>"
    },
    "name": "humanleg_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
deadlineYes
displayAudYes
feeQuoteIdYes
rewardUsdcYes
instructionsYes
evidenceRequirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 behavioral burden. It discloses the important boundary that the tool does not fund or publish the task and that it runs compliance review, but it omits permissions, resulting task status, whether the task is created as a draft, what happens on failed review, and whether the operation is reversible.

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 two short sentences with no filler, and the scope limitation is front-loaded. It is efficient, though "bounded" is not defined and the extreme brevity leaves important details to the schema.

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

Completeness1/5

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

This is a seven-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage. The description does not explain parameter usage, required prerequisites, compliance review behavior, or lifecycle effects beyond saying it does not fund or publish, so it is not complete enough for reliable invocation.

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% for seven required parameters, and the description adds no meaning for any of them. An agent learns nothing about feeQuoteId, rewardUsdc, displayAud, evidenceRequirements, deadline, title, or instructions from the description.

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?

The description states a specific action: creating a task and running compliance review. The second sentence usefully bounds the action by saying it does not fund or publish, which helps distinguish it from downstream lifecycle steps. However, "bounded task" is vague and the description does not clarify how it relates to sibling tools such as fee quote creation.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. The statement that it does not fund or publish is a useful boundary, but it does not say whether a fee quote must precede this call, whether this is a draft step, or when to use the sibling get tools instead.

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