Skip to main content
Glama
Sign In

Handflow

by io.handflow
OverviewDiscussionsAdmin

request_early_access

Ask Handflow for real-world work done by verified people (starting in New York City). Describe the task, place and time. Handflow replies by email with up to 3 options and the total in USD.

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": {
      "email": "<email>",
      "city": "<city>",
      "details": "<details>"
    },
    "name": "request_early_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoNoWho will place the order. Defaults to "agent".
cityYesCity where the work happens
langNoLanguage for our reply. Defaults to "en".
emailYesEmail where Handflow should reply
detailsYesWhat needs doing, where, when, and any budget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the response is asynchronous via email, that you receive up to 3 options, that pricing is quoted as a total in USD, and that coverage is currently limited to New York City. It does not state whether requesting is free/non-binding or what happens if no options exist, which are the remaining gaps.

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?

Three short sentences, front-loaded with the core offer, then the input expectation, then the outcome. Every sentence carries information and there is no filler.

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

Completeness4/5

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

For a five-parameter request tool with no annotations and no output schema, the description covers what is submitted, how the answer arrives, and what the answer contains. Only the commercial terms (free inquiry vs. commitment) and failure mode are left implicit.

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 the schema already documents all five parameters, and the baseline is 3. The description adds modest value by clarifying that email is the reply channel and that details should cover task, place and time, but it says nothing about the who or lang enums beyond what the schema already states.

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 — asking Handflow for real-world work performed by verified people — plus the geographic scope (starting in NYC). It is clearly distinguishable from sign_up_to_earn (the supply side of the marketplace), though it never names that sibling explicitly.

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 description implies the usage case (you need physical, real-world work done and want options quoted), but it gives no explicit when-to-use/when-not guidance and no prerequisites. 'Describe the task, place and time' is input guidance rather than routing guidance.

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

All Handflow 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