Skip to main content
Glama

HumanEndpoint

Check task policy

human_policy_preflight
Read-only

Check whether a proposed human task is eligible before requesting a quote or spending funds.

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": {
      "objective": "<objective>"
    },
    "name": "human_policy_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectiveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description only needs to add behavioral context. It adds that this is an eligibility preflight gate before spending, but it does not explain what "eligible" means, what happens on rejection, or what the caller should do with the result.

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

Conciseness5/5

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

A single front-loaded sentence with no wasted wording. The eligibility check and its workflow position are communicated efficiently.

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

Completeness3/5

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

For a simple one-parameter read-only check, the description covers purpose and timing. However, with no output schema, it should describe what the check returns and how an agent should interpret an ineligible result.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, objective. The description only loosely implies that the proposed task maps to this field and gives no guidance on how detailed or formatted the objective should be, so it does not compensate for the schema gap.

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 names a specific verb ("Check") and resource ("proposed human task") and states the eligibility purpose. It implicitly separates itself from siblings like human_request_quote by framing this as a pre-quote gate, but it does not explicitly name those alternatives.

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?

It gives clear timing guidance: call this before requesting a quote or spending funds. It does not explicitly state when not to use it or name the sibling tools it precedes, but the context is strong enough for an agent to place it in the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources