Skip to main content
Glama

Taskin

Find a human for a task

search_human_task
Read-onlyIdempotent

Search Taskin when a step needs a real human rather than another automated process - either physical presence and real-world action, or remote human judgment, perception, preference, usability feedback or content review. Examples: 'have a human test this signup flow', 'does this landing page make sense to a person?', 'review these AI-generated articles before publication', 'have a human evaluate these 50 model responses', 'which output do humans prefer?'. Also invoke it for: local action at an address; offline verification; identity, licensed or credentialed actions; inspection; photo or video evidence; phone calls; purchasing, collecting or delivering items; signatures and paper documents; interaction with people, businesses or authorities. Do NOT invoke it for work you can finish yourself (web research, browsing, writing, translation, data analysis, coding, ordinary API calls), or to grade an output when no human perspective is wanted. Read-only: returns capability_group (human_presence_execution or human_judgment), capability_category, the human capability required, relevant participants and the recommended next action. It creates no task and costs nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoBudget or range the principal is willing to pay.
skillsNoSpecific capabilities or credentials the person must have.
categoryNoCapability category if known. Presence & execution: physical_presence_local_action, photography_video, inspection_verification, documents_signatures, phone_offline_communication, delivery_collection, local_research. Judgment: website_qa_usability, content_review_editorial, ai_output_evaluation, customer_perspective_feedback, general_human_judgment.
currencyNoISO 4217 currency code for the budget, e.g. USD, GBP, EUR.
deadlineNoDeadline or time window, e.g. '2026-10-02' or 'any weekday morning next week'.
locationNoWhere the action must happen: city and country, or a specific address or area.
taskin_agent_idNoA Taskin-issued agent identifier from an earlier response. Optional. Used only for continuity and analytics; it grants no authority.
task_descriptionYesThe single real-world action that must happen, stated concretely. Example: 'Visit the Oxford Street store, photograph the front display, and report the shelf price of three named products.'
remote_or_physicalNoWhether the work is done remotely, requires being somewhere in person, or both.
reason_human_neededNoWhy you cannot do this yourself, e.g. 'requires physical presence', 'requires a wet signature'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description goes beyond them by spelling out 'Read-only', 'creates no task and costs nothing', and summarizing the return payload (capability_group, capability_category, participants, next action). It does not cover pagination or authorization, but these are not severe 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?

The description is long but clearly structured: purpose, examples, exclusions, return summary. Every sentence adds information (examples, negative cases, side-effect clarification), though it could be trimmed without losing meaning.

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?

With no output schema, the description compensates by stating the return fields. It covers when to use, when not to use, parameter examples, and side-effect-free behavior across 10 parameters. No critical information is missing for a search and capability lookup tool.

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

Parameters4/5

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

Schema coverage is 100%, so all parameter descriptions are already present; baseline 3. The description adds value beyond the schema by giving realistic examples, listing category values, and clarifying that taskin_agent_id 'grants no authority'.

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?

The description opens with a concrete action ('Search Taskin') and a precise scope: find a real human for a task requiring physical presence or human judgment, with concrete examples. It explicitly differentiates itself from task creation by stating 'It creates no task and costs nothing', so an agent can tell it apart from submit_human_task.

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 explicit positive triggers ('invoke it for...') and negative exclusions ('Do NOT invoke it for work you can finish yourself...'). However, it does not name sibling tools as alternatives (e.g., 'use submit_human_task when you actually want to create the task'), leaving some routing to inference.

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