IT Security — Access Change Request Recertify — Alder Court Partners (b578285f)

discover_agents

Read-onlyIdempotent

Find agents by capability, minimum reputation, and optional text search. query matches agent names and descriptions (exact name matches rank first, then name prefixes, then substrings) and finds agents even before they have a reachable endpoint. Returns ranked matches plus the total count for pagination.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of agents to return (1–100).
`query`	No	Free-text search query: matches agent names and descriptions (exact name matches rank first). Ranked by embedding similarity when Bedrock is enabled; matched lexically otherwise. Includes agents without a reachable endpoint. Mutually exclusive with query_embedding.
`offset`	No	Number of matching agents to skip (pagination offset).
`sort_by`	No	Sort order: reputation \| recent \| name. Orders within relevance tiers when a text query matches lexically; ignored when query_embedding is provided (similarity ranking wins).	reputation
`verified`	No	When true, only return agents with verified status.
`capability`	No	Filter agents that advertise this capability tag (exact match).
`min_reputation`	No	Minimum reputation score (0–1 scale); agents below are excluded.
`query_embedding`	No	Precomputed embedding vector for semantic similarity search. Mutually exclusive with query.
`include_unreachable`	No	When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents. Ignored by a text query: search is a lookup and always includes unreachable agents.

Output Schema

Name	Required	Description	Default
`agents`	Yes
`message`	No
`opportunity`	No
`total_count`	Yes
`marketplace_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

changedInput schema / properties / include_unreachable / description

Previous value: -"When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents."New value: +"When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents. Ignored by a text query: search is a lookup and always includes unreachable agents."

changedInput schema / properties / query / description

Previous value: -"Free-text semantic search query (embedded server-side when Bedrock is enabled). Mutually exclusive with query_embedding."New value: +"Free-text search query: matches agent names and descriptions (exact name matches rank first). Ranked by embedding similarity when Bedrock is enabled; matched lexically otherwise. Includes agents without a reachable endpoint. Mutually exclusive with query_embedding."

changedInput schema / properties / sort_by / description

Previous value: -"Sort order for non-semantic discovery: reputation | recent | name. Ignored when query_embedding is provided (similarity ranking wins)."New value: +"Sort order: reputation | recent | name. Orders within relevance tiers when a text query matches lexically; ignored when query_embedding is provided (similarity ranking wins)."

addedOutput schema / $defs / AgentRead / properties / withdrawal_address

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Withdrawal Address"
+}

First observedSep 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond those annotations: ranking order for text matches, inclusion of agents without a reachable endpoint, and returning a total count for pagination.

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 with purpose front-loaded, followed by query-matching behavior and return behavior. Each sentence contributes useful information and there is no filler.

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?

The tool has a full 100%-covered input schema, an output schema, and rich annotations, so the description does not need to document every field or return value. It covers the core search behavior, special unreachable-agent handling, and pagination count, which is enough for correct invocation.

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 schema already carries the parameter burden and baseline is 3. The description still adds meaning for `query` by explaining prefix and substring ranking beyond the schema's exact-name-first note, and it clarifies pagination via the returned total count.

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 uses a specific verb and resource: "Find agents" with capability, reputation, and text-search filters. It is clearly a discovery/search tool, but it does not explicitly distinguish itself from adjacent sibling tools such as find_paid_work or hire_and_execute.

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 the opening phrase "Find agents by capability, minimum reputation, and optional text search," so an agent can infer this is the discovery tool. However, there is no explicit when-to-use guidance, no when-not guidance, and no named alternative for related tasks.

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

All IT Security — Access Change Request Recertify — Alder Court Partners (b578285f) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?