market-pulse

Search the agent directory

pulse_resources

Read-onlyIdempotent

Search the agent directory of models, MCP servers, frameworks, tools, platforms, work lanes and other resources, filtered by kind, category, capability, tags, free tier or GitHub stars and sorted as you choose. Use it to find what exists (for example free open-source MCP servers with 1000+ stars, or models that do video-gen); use pulse_resource_detail for one entry's full record and pulse_lanes when the question is about earning work rather than tooling. Filters combine with AND; omit all to list everything in the directory. Read-only and idempotent. Works without an API key on the free tier. Returns {count, kinds, resources[]}. An unknown kind, sort or argument is refused with the accepted values, never silently ignored.

Input Schema

Name	Required	Description
`q`	No	Free-text match over name, slug, tags and capabilities.
`cap`	No	Capability tag a resource must have, e.g. video-gen, rag, tts.
`tag`	No	Comma-separated tags a resource must carry, all of them.
`free`	No	true = only resources with a free tier; false = only paid ones. A JSON boolean, not the string "true".
`kind`	No	Resource kind to filter by; omit for every kind.
`sort`	No	Sort order; the sorts a kind supports are listed on its directory page.
`category`	No	Category within a kind, as shown on the directory page.
`minStars`	No	Minimum GitHub stars, for open-source entries.

Output Schema

Name	Required	Description
`count`	Yes	Number of resources returned.
`kinds`	Yes	Directory size per resource kind.
`resources`	Yes	Directory entries with slug, name, kind, description, tags, caps and links.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "work-lane",
-  "business-storefront",
-  "model-provider",
-  "model",
-  "model-runner",
-  "autonomous-agent",
-  "ai-library",
-  "security-tool",
-  "agent-framework",
-  "coding-harness",
-  "claw-system",
-  "ide",
-  "ide-plugin",
-  "browser-agent",
-  "skill-source",
-  "mcp-registry",
-  "mcp-server",
-  "build-platform",
-  "social-network",
-  "api-service",
-  "finance-brokerage",
-  "finance-exchange",
-  "crypto-currency",
-  "nft-marketplace",
-  "prediction-market",
-  "monetization-rail",
-  "free-api-keys",
-  "list-repo"
-]New value: +[
+  "work-lane",
+  "business-storefront",
+  "model-provider",
+  "model",
+  "model-runner",
+  "autonomous-agent",
+  "ai-library",
+  "security-tool",
+  "agent-framework",
+  "coding-harness",
+  "claw-system",
+  "ide",
+  "ide-plugin",
+  "browser-agent",
+  "skill-source",
+  "mcp-registry",
+  "mcp-server",
+  "build-platform",
+  "social-network",
+  "api-service",
+  "finance-brokerage",
+  "finance-exchange",
+  "crypto-currency",
+  "nft-marketplace",
+  "prediction-market",
+  "monetization-rail",
+  "free-api-keys",
+  "always-on-agent",
+  "decision-model",
+  "list-repo"
+]

Changed1 schema field changedOct 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of resources returned.",
+      "type": "integer"
+    },
+    "kinds": {
+      "additionalProperties": true,
+      "description": "Directory size per resource kind.",
+      "type": "object"
+    },
+    "resources": {
+      "description": "Directory entries with slug, name, kind, description, tags, caps and links.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "kinds",
+    "resources"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / sort / enum

Previous value: -[
-  "confidence",
-  "grade",
-  "freshness",
-  "name",
-  "stars",
-  "overall-score",
-  "aa-index",
-  "aa-coding",
-  "terminal-bench",
-  "swe-bench",
-  "mmlu",
-  "context",
-  "price-asc",
-  "models-desc",
-  "items"
-]New value: +[
+  "confidence",
+  "grade",
+  "freshness",
+  "name",
+  "stars",
+  "overall-score",
+  "aa-coding",
+  "terminal-bench",
+  "swe-bench",
+  "mmlu",
+  "context",
+  "price-asc",
+  "models-desc",
+  "items"
+]

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / sort / enum

Previous value: -[
-  "confidence",
-  "grade",
-  "freshness",
-  "name",
-  "stars",
-  "overall-score",
-  "terminal-bench",
-  "swe-bench",
-  "mmlu",
-  "context",
-  "price-asc",
-  "models-desc",
-  "items"
-]New value: +[
+  "confidence",
+  "grade",
+  "freshness",
+  "name",
+  "stars",
+  "overall-score",
+  "aa-index",
+  "aa-coding",
+  "terminal-bench",
+  "swe-bench",
+  "mmlu",
+  "context",
+  "price-asc",
+  "models-desc",
+  "items"
+]

First observedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses behavior the agent could not infer: works without an API key on the free tier, filters combine with AND and are omitted to list everything, and invalid kinds/sorts/arguments are rejected with the accepted values rather than silently ignored. That last point is a genuinely useful failure-mode disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and alternatives before the behavioral notes, and every sentence carries information. The sentences are long and clause-dense (the first sentence packs seven resource types plus six filter axes), which costs a little readability.

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 an 8-parameter, all-optional search tool with a full schema and an output schema, the description covers purpose, alternatives, filter combination logic, auth requirement, validation behavior, and return shape. An agent has everything needed to call it correctly on the first try.

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 description coverage is 100%, so the baseline is 3; the description still adds cross-parameter semantics the schema cannot express — AND-combination of filters, all-omitted meaning list-everything, and illustrative filter values. It stops short of explaining individual sorts or the kind/category relationship (explicitly deferred to 'the directory page'), which keeps it off a 5.

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?

Opens with a specific verb and resource ('Search the agent directory of models, MCP servers, frameworks, tools, platforms, work lanes and other resources') and enumerates the filter axes, so the agent knows exactly what corpus is being queried. It also names the siblings it is not (pulse_resource_detail, pulse_lanes), making it distinguishable without opening another schema.

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

Usage Guidelines5/5

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

Gives explicit use cases with concrete examples ('free open-source MCP servers with 1000+ stars, or models that do video-gen') and explicit routing rules: pulse_resource_detail for one entry's full record, pulse_lanes when the question is about earning work rather than tooling. Both the positive and negative conditions are stated.

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

All market-pulse tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.