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

Name	Required	Description
`budget`	No	Budget or range the principal is willing to pay.
`skills`	No	Specific capabilities or credentials the person must have.
`context`	No	Optional. Helps Taskin return better-matched participants and a sharper brief. Leave empty if you prefer; every tool works without it.
`category`	No	Capability 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.
`currency`	No	ISO 4217 currency code for the budget, e.g. USD, GBP, EUR.
`deadline`	No	Deadline or time window, e.g. '2026-10-02' or 'any weekday morning next week'.
`location`	No	Where the action must happen: city and country, or a specific address or area.
`taskin_agent_id`	No	A Taskin-issued agent identifier from an earlier response. Optional. Used only for continuity and analytics; it grants no authority.
`task_description`	Yes	The 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_physical`	No	Whether the work is done remotely, requires being somewhere in person, or both.
`reason_human_needed`	No	Why you cannot do this yourself, e.g. 'requires physical presence', 'requires a wet signature'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional. Helps Taskin return better-matched participants and a sharper brief. Leave empty if you prefer; every tool works without it.",
+  "properties": {
+    "goal": {
+      "description": "Optional. The larger outcome your workflow is working toward (one sentence).",
+      "type": "string"
+    },
+    "principal_type": {
+      "description": "Optional. What kind of principal you act for. Do not include names or contact details here.",
+      "enum": [
+        "individual",
+        "company",
+        "agency_or_reseller",
+        "not_disclosed"
+      ],
+      "type": "string"
+    },
+    "timing": {
+      "description": "Optional. When the human step is needed.",
+      "enum": [
+        "today",
+        "this_week",
+        "later",
+        "no_task_yet"
+      ],
+      "type": "string"
+    },
+    "upstream_step": {
+      "description": "Optional. What your workflow did just before deciding it needs a person.",
+      "type": "string"
+    },
+    "visit_reason": {
+      "description": "Optional. Why you are calling Taskin today.",
+      "enum": [
+        "have_a_task_now",
+        "evaluating_options_for_someone",
+        "building_an_integration",
+        "gathering_facts_to_cite",
+        "testing_the_interface",
+        "other"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, but the description goes further by naming what is returned (capability_group, capability_category, required capability, participants, recommended next action) and by stating the side-effect and cost profile explicitly ('creates no task and costs nothing'). That is real behavioral value beyond the structured hints.

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 routing content is front-loaded and the exclusion clause lands before the return-value sentence, which is the right order. It is somewhat bloated, though: the long list of 'Also invoke it for' scenarios and the partial re-listing of capability categories overlap with the schema enum and cost more tokens than they return.

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 correctly compensates by summarizing the return payload, and it covers the safety/cost profile, usage triggers, exclusions and examples. For an 11-parameter read-only discovery tool, an agent has everything it needs to call this correctly instead of submit_human_task.

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% across all 11 parameters, so the schema carries the semantic load and the baseline is 3. The description only lightly reinforces this via example task descriptions and a restatement of the two capability_group values, which duplicate the category enum rather than adding new syntax or format guidance.

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?

States a specific verb+resource ('Search Taskin when a step needs a real human') and immediately scopes what counts as human work versus automated work. The closing line 'It creates no task and costs nothing' cleanly separates it from the sibling submit_human_task without needing to name it.

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

Usage Guidelines5/5

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

Provides both positive triggers (concrete example phrasings plus an enumerated list of physical, judgment, credential and offline scenarios) and an explicit exclusion clause ('Do NOT invoke it for work you can finish yourself... or to grade an output when no human perspective is wanted'). This is about as close to unambiguous when/when-not routing as a description gets.

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

All Taskin tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?