Skip to main content
Glama
Sign In

Robot Skill Hub

by io.github.Superfast-Robotics
OverviewDiscussionsAdmin

find_robot_skills

Read-onlyIdempotent

Use for broad robotics source/reference discovery or a small candidate-only list. For an executable starting point with prior fixes and setup argv, prefer start_robot_task. Use short task keywords, or query_mode=task with known runtime/robot filters for English sentences. Follow recovery suggestions after empty results. Results distinguish prepared recipes from upstream references; a match is not runtime verification.

Input Schema

NameRequiredDescriptionDefault
qNoDefault all_terms: all query terms must match word prefixes. Standalone A*, D* and RRT* are read as astar, dstar and rrtstar; embedded identifiers and repeated stars keep ordinary tokenization. Empty q browses.
osNo
kindNo
limitNo
robotNo
offsetNo
pythonNo
runtimeNo
controllerNo
hub_commitNo
query_modeNotask opts into ASCII English lexical ranking over at most512 hard-filtered records; narrow runtime/robot when query_too_broad. No execution or compatibility inference.all_terms
observationNo
architectureNo
runtime_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / q / description
      Previous value: -"All query terms must match word prefixes. Standalone A*, D* and RRT* are read as astar, dstar and rrtstar; embedded identifiers and repeated stars keep ordinary tokenization. Empty q browses."New value: +"Default all_terms: all query terms must match word prefixes. Standalone A*, D* and RRT* are read as astar, dstar and rrtstar; embedded identifiers and repeated stars keep ordinary tokenization. Empty q browses."
    • addedInput schema / properties / query_mode
      Added value: +{
+  "default": "all_terms",
+  "description": "task opts into ASCII English lexical ranking over at most512 hard-filtered records; narrow runtime/robot when query_too_broad. No execution or compatibility inference.",
+  "enum": [
+    "all_terms",
+    "task"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / q / description
      Added value: +"All query terms must match word prefixes. Standalone A*, D* and RRT* are read as astar, dstar and rrtstar; embedded identifiers and repeated stars keep ordinary tokenization. Empty q browses."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile needs no restatement. The description adds genuinely useful behavior: results distinguish prepared recipes from upstream references, a match is not runtime verification, and empty results come with recovery suggestions.

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?

Roughly five short sentences, front-loaded with what the tool is for and the sibling alternative before query tips. Dense but each sentence carries distinct information; 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?

With no output schema, the description usefully explains what results mean (recipe vs upstream reference, not runtime verification) and covers empty-result recovery. It omits pagination behavior despite limit/offset params and doesn't state defaults, which is a minor gap.

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 only 14% across 14 params, so the description carries a heavy burden and only partially meets it — it clarifies q usage and query_mode=task semantics and implies runtime/robot act as filters, but 12 params (os, kind, limit, offset, hub_commit, architecture, etc.) get no semantic guidance such as exact vs prefix matching.

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 states the tool's role as broad robotics source/reference discovery or a small candidate-only list, which is clear enough to separate it from start_robot_task. It lacks a crisp verb+resource phrase of its own (the name carries 'find'), but the scope and result nature are stated.

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?

It names the alternative explicitly (“prefer start_robot_task”) along with the selecting condition (executable starting point with prior fixes and setup argv). It also gives query-shaping guidance (short keywords vs query_mode=task with runtime/robot filters) and instructs following recovery suggestions after empty results.

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

All Robot Skill Hub toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources