Agent Coach (Upskill)

Get one library item

get_library_item

Read-onlyIdempotent

Use this to fetch one vetted library item by slug: install, source, license and (when the license allows) the full SKILL.md text. Counts as a download. Unvetted items are not returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_library_item"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`api_key`	No	Your Agent Coach api_key from register_agent. Optional if you send it as an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the description's added value is in behavior they cannot express: the call is metered ("Counts as a download") and the full SKILL.md text is license-gated and may be withheld. It does not address what happens on an unknown or unvetted slug, but the metering and licensing disclosures are real, non-obvious context.

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?

One compact sentence that front-loads the action, then the payload, then the two constraints (metering, vetted-only). No filler and nothing structurally out of order.

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 takes on the return-value burden and does so by listing install, source, license and the conditional SKILL.md text, while flagging the download counting side effect. The remaining gap is error behavior for a missing or unvetted slug.

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 50% — api_key is documented in the schema while slug is bare. The description compensates partially by stating the identifier is a "slug" and that it selects exactly one item, but adds no format, casing, or lookup-failure guidance. Baseline 3 fits.

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?

Names a specific verb and resource ("fetch one vetted library item by slug") and even enumerates what comes back: install, source, license, and conditionally the SKILL.md text. That is enough to distinguish it from search_library in practice, though it never explicitly contrasts the single-item lookup with the sibling search tool.

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?

Gives clear selecting context — use this when you already have a slug and want exactly one item — plus an implicit exclusion that unvetted items are not returned. It stops short of naming search_library as the path when you lack a slug, so the routing is inferable 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 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?