Skip to main content
Glama

xyz MCP by CyberXYZ

search

Read-only

Find a package by name across every ecosystem (exact match first, then prefix, then most advisories), with its advisory count and worst severity. Use it when you do not know a package's ecosystem or exact spelling; then call package_info or check_package.

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
limitNoMax results (1-25)
queryYesPackage name or part of one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by explaining the match-ranking behavior and what each result contains. It says nothing about result-set size behavior or how the ranked list interacts with the limit, so with annotations carrying the safety burden a 3 fits.

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, no filler, with the core action and ranking rule front-loaded and the routing advice last. Every clause carries information the agent needs.

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?

There is no output schema, and the description compensates by naming the returned fields (advisory count, worst severity). Combined with the annotations and full schema coverage on two parameters, nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by clarifying how the query string is interpreted (exact match first, then prefix, then most advisories) – matching semantics the schema does not state. The limit parameter is left entirely to the schema.

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?

States a specific verb and resource ('Find a package by name across every ecosystem') and goes further by disclosing the result ordering (exact match, then prefix, then most advisories) and what comes back (advisory count, worst severity). That is enough for an agent to distinguish it from package_info and check_package without opening any 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?

Gives an explicit trigger condition ('when you do not know a package's ecosystem or exact spelling') plus a follow-up path ('then call package_info or check_package'). It stops short of a true when-not clause or a named competing tool, so it lands at 4 rather than 5.

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