demand_pulsePublic, k-anonymous demand signal from the directory: trending searches, most-saved and most-installed tools. Aggregates only — sourced from ≥5 distinct anonymous sessions per entry.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| most_saved | Yes | ||
| most_installed | Yes | ||
| trending_searches | Yes | ||
| total_interactions | Yes |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "most_installed": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "category": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "sessions": {
+ "type": "number"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "slug",
+ "category",
+ "sessions"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "most_saved": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "category": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "sessions": {
+ "type": "number"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "slug",
+ "category",
+ "sessions"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_interactions": {
+ "type": "number"
+ },
+ "trending_searches": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "query": {
+ "type": "string"
+ },
+ "sessions": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "query",
+ "sessions"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "total_interactions",
+ "trending_searches",
+ "most_saved",
+ "most_installed"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: the k-anonymity guarantee (≥5 distinct anonymous sessions per entry) and the 'Aggregates only' privacy constraint, which are important behavioral traits not visible in the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no waste. The first sentence states the core purpose and data types; the second adds the critical privacy/aggregation constraint. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only tool with an output schema present, the description is complete. It explains what the tool returns, the privacy model, and the aggregation source. The output schema presumably details the response structure, so the description doesn't need to.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, so there is no parameter semantics to document. The description compensates by explaining what the output represents (trending searches, most-saved, most-installed) and the aggregation guarantee, which is the closest thing to parameter semantics for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a public, k-anonymous demand signal from the directory, listing the specific data types it provides (trending searches, most-saved, most-installed tools). It distinguishes itself from sibling tools like search_skills or get_skill by emphasizing aggregated, anonymous demand data rather than individual tool details or collections.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for retrieving aggregate demand signals, and the 'Public' label plus 'Aggregates only' clarifies when it's appropriate. It doesn't explicitly name alternatives or state when not to use it, but the context signals (0 params, read-only) and sibling names make the use case clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.