Skip to main content
Glama

Search FTC Knowledge

search_knowledge
Read-only

Search FTC knowledge base for documentation, code examples, and hardware API references. Retrieve verified information to aid robot code development.

Instructions

Search FTC knowledge base. Finds documentation, code examples, and hardware API references.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query, example topic, or device name
Behavior3/5

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

Description adds context about content types beyond the readOnlyHint annotation but omits details like return format, pagination, or rate limits. It does not contradict annotations.

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 concise, front-loaded sentences with no redundant information. Every word adds value.

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 simple search tool with one parameter and no output schema, the description adequately covers purpose and scope. However, it could improve by hinting at result behavior (e.g., returns relevant snippets).

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?

The single parameter 'query' is fully described in the schema (100% coverage). The tool description adds no extra semantic value, so baseline score of 3 applies.

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?

Description clearly states the verb 'Search' and resource 'FTC knowledge base'. It lists specific content types (documentation, code examples, hardware API references) that distinguish it from sibling tools like scan_project and validate_ftc_code.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description does not mention when to prefer search_knowledge over scan_project or validate_ftc_code, making it ambiguous for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jackulau/ftcMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server