Skip to main content
Glama
Sign In
toolradar-mcp

toolradar-mcp

by Nadeus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_tools

Search and filter 10,000+ software tools by query, category, pricing, and sort order; get names, descriptions, pricing, scores, and categories, with a not_listed note for products not in the catalog.

Instructions

Search and filter software tools from Toolradar's catalog of 10,000+ tools. Returns tools with names, descriptions, pricing, scores, and categories. A product name we do not list comes back with a not_listed note instead of a lookalike.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: score (editorial rating), recent (newest first), rating (user review rating)
limitNoNumber of results (default 10, max 50)
queryNoSearch query (e.g. 'project management', 'AI writing tool')
pricingNoFilter by pricing model
categoryNoFilter by category slug (e.g. 'project-management', 'ai-writing')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order: score (editorial rating), recent (newest), trending (most upvotes this week)"New value: +"Sort order: score (editorial rating), recent (newest first), rating (user review rating)"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "score",
-  "recent",
-  "trending"
-]New value: +[
+  "score",
+  "recent",
+  "rating"
+]
  2. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses returned fields and the important not_listed fallback instead of a lookalike result, but it does not mention read-only nature, permissions, rate limits, or pagination behavior beyond what the schema implies.

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 tight sentences. Scope, return contents, and the not_listed edge case are front-loaded with no redundant wording.

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 five-parameter search tool with no output schema, the description adequately explains the catalog scope, returned fields, and an important edge case. It could be more complete by clarifying how it relates to sibling discovery tools and by mentioning permission or rate-limit expectations.

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%, so all five parameters are already documented in the input schema. The description does not add syntax, default, or filtering details beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: search and filter software tools from a named catalog. It adds useful scope with '10,000+ tools' and distinguishes itself from a point lookup like get_tool, though it does not explicitly contrast with siblings such as recommend_tools or list_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Search and filter', and the not_listed behavior gives useful context for product-name searches. However, the description does not state when to use this versus get_tool, compare_tools, recommend_tools, or list_categories.

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