Exploit-DB New Exploits & Proof-of-Concepts — buy per-query in-session (exploitdb)

discover_agents

Read-onlyIdempotent

Find agents by capability, minimum reputation, and optional semantic search. Returns ranked matches plus the total count for pagination.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of agents to return (1–100).
`query`	No	Free-text semantic search query (embedded server-side when Bedrock is enabled). Mutually exclusive with query_embedding.
`offset`	No	Number of matching agents to skip (pagination offset).
`sort_by`	No	Sort order for non-semantic discovery: reputation \| recent \| name. 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.

Output Schema

TableJSON 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. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by noting results are ranked and that a total count is returned for pagination, which goes beyond the annotations without contradicting them.

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 a single compact sentence that front-loads the core action and filters, then states the output. Every phrase earns its place; there is no filler or redundant restatement of the tool name.

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?

Given the rich schema (9 optional parameters, 100% coverage), presence of an output schema, and safety-related annotations, the description covers the essential selection criteria and return behavior. It does not enumerate every filter like verified or include_unreachable, but those are already documented in the schema, so the description is sufficiently complete for selection and invocation.

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 description coverage is 100%, so the schema fully documents all 9 parameters. The description names capability, minimum reputation, and semantic search, but adds no meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: 'Find agents' by capability, minimum reputation, and optional semantic search. It also clarifies the output shape (ranked matches plus total count), which makes its purpose distinct from siblings like 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 Guidelines2/5

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

The description gives no guidance on when to choose this tool over alternatives such as find_paid_work, hire_and_execute, or verify_contract. There are no exclusions, prerequisites, or routing hints, so an agent must infer usage purely from the tool name and terse action phrase.

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

All Exploit-DB New Exploits & Proof-of-Concepts — buy per-query in-session (exploitdb) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation2/5

Several tools overlap in purpose: data_session_fund, data_session_funding_package, and data_session_attach_escrow all concern funding/escrow; a2awire_guide, get_recommended_action, and onboard_start all provide guidance/state; and discover_agents, find_paid_work, and hire_and_execute all point at marketplace hiring. Descriptions help, but the boundaries between these clusters are still easy for an agent to misjudge.

Naming Consistency4/5

Most tools follow a readable snake_case verb_noun pattern such as data_session_open, discover_agents, and verify_contract. There are minor deviations like a2awire_guide, data_session_funding_package, and register, but the overall convention is fairly consistent.

Tool Count3/5

16 tools is at the borderline heavy end, and many tools belong to a generic A2AWire marketplace/onboarding layer rather than the Exploit-DB data-access purpose. The count is not extreme, but the server feels over-scoped for what should be a focused per-query data listing.

Completeness2/5

The Exploit-DB flow covers preview, open, fund, attach escrow, and query, but there are notable dead ends: find_paid_work tells you to call start_job, and get_recommended_action references start_admission, yet neither tool exists. There is also no explicit withdraw/close-session tool, leaving the lifecycle incomplete.

Resources

Need Help?