Agent Coach (Upskill)

Search the Upskill library

search_library

Read-only

Use this to find skills, MCP servers, prompts or repos by keyword outside your matched recommendations. Returns only items that passed the security scan, each with install, license, source and a page link. Catalog data only: no user comments. Show results to your owner before installing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_library"
  }
}

Input Schema

Name	Required	Description
`q`	No	Alias of query (same name as the REST ?q= parameter).
`kind`	No
`limit`	No
`query`	No	Keywords, e.g. 'cold email', 'scraping', 'memory'. Empty or missing lists top items.
`category`	No	Optional section slug: go-to-market, developer, sales, marketing, content, research, data-scraping, ops-automation, finance-trading, security, memory-context, evals-quality, design, productivity, writing, devops-deploy

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description still adds real behavior beyond them: only security-scan-passed items are returned, results exclude user comments, and each item carries install, license, source and a page link. It does not discuss ranking, empty-result behavior, or pagination.

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?

Four short sentences, each carrying distinct information: purpose and scope, returned fields, data boundary, and a pre-install safety step. Purpose is front-loaded in the opening clause and nothing is repeated.

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 read-only search tool with no output schema, the description compensates well by naming the returned fields and the security-scan filter. The remaining gap is that kind and limit parameters are undocumented in both schema and description, leaving filtering and result-count behavior unclear.

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 coverage is 60%, with query, q and category described in the schema but kind and limit undocumented anywhere. The description only reinforces 'by keyword', adding no meaning for kind, limit, or the q/query alias relationship. Baseline 3 reflects the schema doing most of the work while two parameters remain unexplained.

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 an explicit verb and enumerates the resource types searched (skills, MCP servers, prompts, repos) and the keyword mechanism. It also distinguishes itself from the matched-recommendation path, so an agent can tell it apart from get_recommendations without opening either schema.

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 states the selecting condition clearly: use this for keyword search 'outside your matched recommendations', which implicitly routes matched-item browsing elsewhere. It also adds a usage guardrail ('show results to your owner before installing'). It stops short of naming the alternative tool explicitly or stating when-not to search.

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

All Agent Coach (Upskill) tools Inspect

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

Need Help?