Skip to main content
Glama
Sign In
Deadzone

Deadzone

by laradji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

search_libraries

Resolve library names to ranked library ID and version candidates for documentation search. List top libraries by document count when no name is given.

Instructions

Resolve a free-text library name into a ranked list of (lib_id, version) candidates that can be passed to search_docs. Returns one entry per indexed (lib_id, version) pair — group by lib_id on the client to see the versions of the same library. Pass an empty name to list the most-indexed libraries by doc_count.

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_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNofree-text library name to resolve; empty returns top libs by doc count
limitNomax results, default 10, max 50

Output Schema

NameRequiredDescriptionDefault
librariesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It explains that the tool returns one entry per (lib_id, version) pair and advises grouping by lib_id on the client. It also describes the behavior for empty input. No contradictions or omissions noted.

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?

The description is three sentences long, front-loaded with the main purpose, and each sentence adds essential information. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only two parameters, an output schema, and no nested objects, the description covers all necessary aspects: main use, special case, output format, and relationship to sibling tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes all parameters, the description adds important context: the meaning of an empty name and the output structure (one entry per pair, need to group). This goes beyond the schema's basic descriptions.

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 uses the verb 'Resolve' and specifies the resource ('free-text library name'). It clearly states the output: a ranked list of (lib_id, version) candidates that can be passed to search_docs. It also distinguishes from sibling 'search_docs' by indicating the output is intended for it, and clarifies behavior for empty input.

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?

The description explicitly states when to use this tool: to resolve a library name into candidates for search_docs. It also explains the special case of passing an empty name to list most-indexed libraries. While it doesn't state when not to use it, the purpose and boundary are clear enough.

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

Deploy Server

Other Tools