There's An AI For That

Search robots

search_robots

Read-only

Search and compare robots by name, description, specifications, type, use case, maker, and linked task. Supports hardware filters and sorting.

Input Schema

Name	Required	Description	Default
`sort`	No		relevance
`task`	No	Exact TAAFT task name or slug. Matches primary and secondary task links.
`limit`	No
`query`	No	Optional free-text robot capability, product, use case, specification, or maker query.
`status`	No	Exact availability status, such as Pilot or Commercially available.
`use_case`	No	Exact primary use case, such as Warehousing & Logistics or Productivity.
`max_price`	No	Maximum listed price, inclusive.
`min_price`	No	Minimum listed price, inclusive.
`robot_type`	No	Exact robot type, such as Warehouse, Home, or Humanoid.
`autonomy_level`	No	Exact autonomy level, such as Teleoperated or Fully autonomous.
`release_date_to`	No	Latest release date, inclusive, in YYYY-MM-DD format.
`release_date_from`	No	Earliest release date, inclusive, in YYYY-MM-DD format.
`manufacturing_country`	No	Manufacturing country name or two-letter country code.

Output Schema

Name	Required	Description	Default
`robots`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 13, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "required": [
+      "robot_type"
+    ]
+  },
+  {
+    "required": [
+      "autonomy_level"
+    ]
+  },
+  {
+    "required": [
+      "status"
+    ]
+  },
+  {
+    "required": [
+      "use_case"
+    ]
+  },
+  {
+    "required": [
+      "min_price"
+    ]
+  },
+  {
+    "required": [
+      "max_price"
+    ]
+  },
+  {
+    "required": [
+      "manufacturing_country"
+    ]
+  },
+  {
+    "required": [
+      "release_date_from"
+    ]
+  },
+  {
+    "required": [
+      "release_date_to"
+    ]
+  },
+  {
+    "required": [
+      "task"
+    ]
+  }
+]

addedInput schema / properties / autonomy_level

Added value: +{
+  "description": "Exact autonomy level, such as Teleoperated or Fully autonomous.",
+  "enum": [
+    "Teleoperated",
+    "Assisted",
+    "Semi-autonomous",
+    "Fully autonomous"
+  ],
+  "type": "string"
+}

addedInput schema / properties / manufacturing_country

Added value: +{
+  "description": "Manufacturing country name or two-letter country code.",
+  "type": "string"
+}

addedInput schema / properties / max_price

Added value: +{
+  "description": "Maximum listed price, inclusive.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / min_price

Added value: +{
+  "description": "Minimum listed price, inclusive.",
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / properties / query / description

Previous value: -"Robot name to search for."New value: +"Optional free-text robot capability, product, use case, specification, or maker query."

addedInput schema / properties / release_date_from

Added value: +{
+  "description": "Earliest release date, inclusive, in YYYY-MM-DD format.",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / release_date_to

Added value: +{
+  "description": "Latest release date, inclusive, in YYYY-MM-DD format.",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / robot_type

Added value: +{
+  "description": "Exact robot type, such as Warehouse, Home, or Humanoid.",
+  "enum": [
+    "Humanoid",
+    "Mobile",
+    "Manipulator",
+    "Drone",
+    "Industrial",
+    "Warehouse",
+    "Healthcare",
+    "Home",
+    "Agricultural",
+    "Defense",
+    "Service",
+    "Companion",
+    "Other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "default": "relevance",
+  "enum": [
+    "relevance",
+    "price",
+    "latest",
+    "popular"
+  ],
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Exact availability status, such as Pilot or Commercially available.",
+  "enum": [
+    "Announced",
+    "In development",
+    "Prototype",
+    "Pilot",
+    "Pre-order",
+    "In production",
+    "Commercially available",
+    "Paused",
+    "Discontinued",
+    "Cancelled",
+    "Waitlist"
+  ],
+  "type": "string"
+}

addedInput schema / properties / task

Added value: +{
+  "description": "Exact TAAFT task name or slug. Matches primary and secondary task links.",
+  "type": "string"
+}

addedInput schema / properties / use_case

Added value: +{
+  "description": "Exact primary use case, such as Warehousing & Logistics or Productivity.",
+  "enum": [
+    "Manufacturing",
+    "Warehousing & Logistics",
+    "Healthcare",
+    "Elder Care",
+    "Surgery",
+    "Agriculture",
+    "Construction",
+    "Inspection",
+    "Security",
+    "Defense",
+    "Retail",
+    "Hospitality",
+    "Home Assistance",
+    "Education",
+    "Research",
+    "Disaster Response",
+    "Other"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[]

addedOutput schema / properties / robots / items / properties / availability
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / robots / items / properties / maker
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / robots / items / properties / price
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / robots / items / properties / price_currency
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / robots / items / properties / primary_use_cases

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / robots / items / properties / tasks

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "role": {
+        "enum": [
+          "primary",
+          "secondary"
+        ],
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "role",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / robots / items / properties / types

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / robots / items / required

Previous value: -[
-  "id",
-  "entity_type",
-  "name",
-  "slug",
-  "url"
-]New value: +[
+  "id",
+  "entity_type",
+  "name",
+  "slug",
+  "url",
+  "description",
+  "price",
+  "price_currency",
+  "types",
+  "primary_use_cases",
+  "maker",
+  "availability",
+  "tasks"
+]

AddedSep 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that hardware filters and sorting are supported; it does not disclose result paging, default/max limits, or the anyOf constraint requiring at least one filter, which is a genuinely useful behavioral detail it omits.

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?

Two sentences, zero filler, with the core capability front-loaded before the secondary note about filters and sorting. Every clause carries information.

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?

An output schema exists and annotations cover the safety profile, so return values and read-only semantics need not be restated. The description is nearly complete for a filtered search tool, missing only the mandatory-criterion rule and pagination behavior, both of which an agent would benefit from knowing up front.

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 85%, so the schema already documents nearly every parameter with enums, defaults, and formats. The description's facet list loosely maps to those parameters (type, use case, maker/query, task) but adds no syntax, matching semantics, or range behavior beyond what the schema states; baseline 3 applies.

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 (search and compare) and resource (robots) and enumerates the searchable facets: name, description, specifications, type, use case, maker, and linked task. It is clearly distinct from get_robot, but it never names or contrasts with the search_* sibling family, so sibling differentiation is left to the name alone.

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?

"Search and compare robots" implies retrieval usage but gives no when-to-use conditions, no indication of when to prefer get_robot for a single lookup, and no note that at least one filter criterion is mandatory. Usage is inferable from the tool name rather than stated.

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

All There's An AI For That tools Inspect

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.