ground-truth-mcp

Package Market Search

estimate_market

Read-onlyIdempotent

Estimate market crowdedness for a package category by searching npm or PyPI to see live result counts and representative matches, validating if the market is empty, niche, or competitive.

Instructions

Search npm or PyPI to estimate how crowded a package category is before you claim that a market is empty, niche, or competitive. Use this when you have a category or search phrase such as 'edge orm' and want live result counts plus representative matches. Do not use it to compare exact known package names or to infer adoption from downloads; it reflects search results, not market share. Registry responses are cached for 5 minutes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Short registry search phrase to evaluate, for example 'mcp memory server' or 'edge orm'.
`registry`	No	Registry to search. Use 'npm' for JavaScript ecosystems and 'pypi' for Python ecosystems.	npm

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Search phrase that was evaluated.
`registry`	Yes	Registry that was searched.
`totalResults`	Yes	Total number of matching packages reported by the registry search.
`topResults`	Yes	Representative top search matches that help interpret the market count.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Apr 30, 2026

changedInput schema / properties / query / description

Previous value: -"Search query (e.g. 'mcp memory server')"New value: +"Short registry search phrase to evaluate, for example 'mcp memory server' or 'edge orm'."

addedInput schema / properties / query / minLength
```
Added value: +2
```

changedInput schema / properties / registry / description

Previous value: -"Which registry to search"New value: +"Registry to search. Use 'npm' for JavaScript ecosystems and 'pypi' for Python ecosystems."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "query": {
+      "description": "Search phrase that was evaluated.",
+      "type": "string"
+    },
+    "registry": {
+      "description": "Registry that was searched.",
+      "enum": [
+        "npm",
+        "pypi"
+      ],
+      "type": "string"
+    },
+    "topResults": {
+      "description": "Representative top search matches that help interpret the market count.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "description": "Short package summary from registry metadata.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Package name returned by the registry.",
+            "type": "string"
+          },
+          "score": {
+            "description": "Registry relevance score when npm provides one.",
+            "type": "string"
+          },
+          "version": {
+            "description": "Latest version string returned in the result payload.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description",
+          "version"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "anyOf": [
+        {
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Total number of matching packages reported by the registry search."
+    }
+  },
+  "required": [
+    "query",
+    "registry",
+    "totalResults",
+    "topResults"
+  ],
+  "type": "object"
+}

First observedv0.1.0Apr 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive. The description adds valuable behavioral context: responses are cached for 5 minutes, and results reflect search relevance not market share, which complements the annotations without contradiction.

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?

Four concise sentences deliver purpose, usage, exclusions, and caching behavior with no filler. The most important information is front-loaded in the first sentence.

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?

For a two-parameter read-only search tool with an output schema and rich annotations, the description covers key behaviors, limitations, and cache behavior. It is fully adequate for an agent to select and invoke the tool correctly.

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 100% with descriptive text for both query and registry. The description itself adds only an example phrase ('edge orm') and reiterates the npm/PyPI choice, providing no additional semantic value beyond the schema, so baseline 3 applies.

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?

Clearly states the tool searches npm or PyPI to estimate package category crowdedness before making market claims. This is a specific verb-resource-purpose combination that distinguishes it from sibling tools focused on compliance, endpoints, pricing, and monitors.

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?

Explicitly states when to use it ('when you have a category or search phrase') and what not to use it for ('Do not use it to compare exact known package names or to infer adoption from downloads'). However, it does not name a specific alternative tool, slightly reducing the guidance completeness.

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

Deploy Server