AgentsJunction

Discover resources

discover

Find agents and MCP servers for a natural-language task. Filter by resource type, protocol, callability, health availability, authentication, capability evidence, skill, source, and freshness; paginate with page and limit. Returns ranked candidates with match reasons. Location, language, pricing, and side-effect metadata are not indexed yet and are reported in meta.unsupportedFilters. Unknown states never satisfy known-state filters.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	One-based result page; defaults to 1.
`task`	Yes	Natural-language task used to rank relevant resources.
`limit`	No	Results per page; defaults to 10.
`skill`	No	Filter agents by a declared skill ID, name, description, or tag.
`trust`	No
`source`	No	Filter by exact catalog source, such as self-registered or official-registry.
`pricing`	No	Filter by structured pricing metadata; currently not indexed.
`callable`	No	Filter by direct endpoint callability.
`language`	No	Match any listed language; currently not indexed.
`location`	No	Filter by structured location metadata; currently not indexed.
`protocol`	No	Return only resources that support this protocol, such as a2a or mcp.
`freshness`	No	Require a catalog update timestamp within this many days.
`protocols`	No
`apiVersion`	No
`sideEffects`	No	Require all listed side effects; currently not indexed.
`availability`	No	Require this latest health state; missing or stale checks are unknown.
`requirements`	No
`resourceType`	No	Return only this resource type.
`resourceTypes`	No
`authentication`	No	Filter by authentication requirement; unknown metadata does not match none or required.
`protocolVersions`	No
`verificationState`	No	Require an exact capability evidence state.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 4, 2026

addedInput schema / properties / authentication

Added value: +{
+  "description": "Filter by authentication requirement; unknown metadata does not match none or required.",
+  "enum": [
+    "unknown",
+    "none",
+    "required"
+  ],
+  "type": "string"
+}

addedInput schema / properties / availability

Added value: +{
+  "description": "Require this latest health state; missing or stale checks are unknown.",
+  "enum": [
+    "unknown",
+    "online",
+    "degraded",
+    "offline"
+  ],
+  "type": "string"
+}

addedInput schema / properties / callable

Added value: +{
+  "description": "Filter by direct endpoint callability.",
+  "type": "boolean"
+}

addedInput schema / properties / freshness

Added value: +{
+  "description": "Require a catalog update timestamp within this many days.",
+  "properties": {
+    "withinDays": {
+      "maximum": 3650,
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "withinDays"
+  ],
+  "type": "object"
+}

addedInput schema / properties / language

Added value: +{
+  "description": "Match any listed language; currently not indexed.",
+  "items": {
+    "maxLength": 35,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

addedInput schema / properties / limit / description

Added value: +"Results per page; defaults to 10."

addedInput schema / properties / location

Added value: +{
+  "description": "Filter by structured location metadata; currently not indexed.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "One-based result page; defaults to 1.",
+  "maximum": 100000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / pricing

Added value: +{
+  "description": "Filter by structured pricing metadata; currently not indexed.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / protocol

Added value: +{
+  "description": "Return only resources that support this protocol, such as a2a or mcp.",
+  "maxLength": 40,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / resourceType

Added value: +{
+  "description": "Return only this resource type.",
+  "enum": [
+    "agent",
+    "mcp-server",
+    "skill",
+    "knowledge-resource",
+    "gateway",
+    "tool",
+    "repository",
+    "website",
+    "documentation"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sideEffects

Added value: +{
+  "description": "Require all listed side effects; currently not indexed.",
+  "items": {
+    "enum": [
+      "read",
+      "write",
+      "delete",
+      "purchase",
+      "message",
+      "execute",
+      "external-side-effect"
+    ],
+    "type": "string"
+  },
+  "maxItems": 7,
+  "type": "array"
+}

addedInput schema / properties / skill

Added value: +{
+  "description": "Filter agents by a declared skill ID, name, description, or tag.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Filter by exact catalog source, such as self-registered or official-registry.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / task / description

Added value: +"Natural-language task used to rank relevant resources."

addedInput schema / properties / verificationState

Added value: +{
+  "description": "Require an exact capability evidence state.",
+  "enum": [
+    "detected",
+    "claimed",
+    "tested",
+    "verified"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / protocolVersions

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "maxLength": 40,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  },
+  "propertyNames": {
+    "maxLength": 40,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "object"
+}

AddedOct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that results are ranked with match reasons, that unsupported facets surface in meta.unsupportedFilters, and that 'unknown states never satisfy known-state filters' — a non-obvious matching semantic. It omits auth/rate-limit behavior, but for a read-only discovery call the disclosure is above baseline.

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?

Purpose is front-loaded in the first sentence, and the remaining clauses pack filter scope, pagination, return shape, and unsupported-filter reporting into dense but non-redundant prose. The filter list is long but justified by a 22-parameter schema.

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 22-parameter, no-annotation, no-output-schema tool, the description covers the essentials: what it returns (ranked candidates with match reasons), how to paginate, and where unsupported filters are reported. Gaps remain around the nested trust/requirements/protocolVersions objects and result cardinality, so it is not fully complete.

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 73% and the description groups the filter facets (resource type, protocol, callability, availability, authentication, capability evidence, skill, source, freshness) into a coherent map, plus adds the unknown-does-not-match-known semantics that the schema only states for some params. It adds genuine meaning over the schema, though it does not explain the trust/verificationState or protocolVersions structures.

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?

States a specific verb and resource set: 'Find agents and MCP servers for a natural-language task.' It is clearly a discovery/search tool rather than a fetch tool, but it never names the obvious siblings (search_agents, search_servers) that an agent would weigh against it, so differentiation is left to inference.

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?

The description enumerates what can be filtered and that results are paginated, which implies when the tool is useful, but it gives no explicit when-to-use guidance or routing against siblings like search_agents/search_servers/get_agent. Usage is implied rather than stated.

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

All AgentsJunction 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.

Resources

Need Help?