Skip to main content
Glama

PickZeal

Search PickZeal

search
Read-only

Search PickZeal tools and articles by keyword, for example "merge pdf", "word count" or "llm 8gb ram". Returns titles, URLs and short descriptions, best match first.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoLimit results to tools or articles. Omit for both.
limitNoMaximum results (default 10)
queryYesSearch words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's main added value is telling the agent what comes back ('titles, URLs and short descriptions') and that results are ranked 'best match first'. That ranking and return-shape disclosure is genuinely useful beyond the annotations, though it says nothing about empty-result or no-match behavior.

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 sentences, front-loaded with the verb and resource, then the return contract. The inline examples do real work and there is no filler or restatement of the tool name.

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 3-parameter read-only search with no output schema, the description covers purpose, input style, return fields, and ordering, which is close to enough to call it correctly. The remaining gap is absence of any statement about zero-result handling or result volume relative to the limit parameter.

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 100% and the enum and limit bounds are fully documented in the schema, so the baseline is 3. The description adds only indirect guidance on query phrasing through examples; it does not explain how query words are matched (AND vs OR, stemming) or how limit interacts with ranking.

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 names a specific verb and resource ('Search PickZeal tools and articles') and scopes it to keyword matching, with concrete example queries that anchor what counts as a keyword. It does not explicitly differentiate itself from the list_articles/list_tools siblings (i.e., that this is for keyword lookup while those enumerate), so it stops short of a 5.

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 example queries ('merge pdf', 'word count', 'llm 8gb ram') make clear what kind of input this tool is for, so an agent can tell when a keyword search is the right call. There is no explicit when-not guidance or routing to the list siblings for browsing an entire catalog.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources