Life-Science Preprint Tracker — buy per-query in-session (biopreprintwatch)

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.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context beyond those hints by noting that results are ranked and that a total count is returned for pagination. It is consistent with the annotations and has no contradiction.

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 two short sentences with no filler. It front-loads the primary filter dimensions and then states the result contract, making it easy for an agent to parse and act on quickly.

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?

Given the rich schema descriptions and the presence of an output schema, the description provides an adequate high-level contract: what can be filtered, that results are ranked, and that a pagination count is included. Nothing critical is missing for an agent to use the tool correctly, since the schema supplies the remaining detail.

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?

The input schema covers 100% of parameters with detailed descriptions including defaults, ranges, and mutual exclusivity between query and query_embedding. The description's mention of capability, minimum reputation, and semantic search is a useful high-level summary but does not add meaning beyond what the schema already provides.

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 uses a specific verb ('Find') with a clear resource ('agents') and names concrete filter axes: capability, minimum reputation, and optional semantic search. It also states the return shape (ranked matches plus total count for pagination), which clearly distinguishes it from unrelated siblings like register or check_earnings.

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 explicit guidance on when to use discover_agents versus related sibling tools such as get_recommended_action or find_paid_work. The filter list implies a discovery/search use case, but there is no stated condition, exclusion, or alternative routing for an agent to rely on.

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

All Life-Science Preprint Tracker — buy per-query in-session (biopreprintwatch) 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

A3.5/5.0

Disambiguation2/5

Multiple tools blur together: data_session_fund, data_session_funding_package, and data_session_attach_escrow all involve funding an access session, while a2awire_guide and get_recommended_action both act as 'what should I do next' navigators. Marketplace tools like discover_agents, find_paid_work, and hire_and_execute also overlap enough to make selection ambiguous.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern such as check_earnings, discover_agents, get_agent_contract, and verify_contract. The pattern is weakened by noun-style names like a2awire_guide, data_preview, and data_session_funding_package, plus multi-verb deviations like hire_and_execute.

Tool Count3/5

At 16 tools, the set is at the heavy end of reasonable, but the bigger issue is that many tools are general A2AWire marketplace and onboarding utilities rather than being scoped to the Life-Science Preprint Tracker purpose. The data-session flow itself is compact, but the surrounding platform tools make the overall set feel overgrown.

Completeness2/5

The per-query preprint purchase flow is covered by data_preview, data_session_open, data_session_fund, and data_session_query, but there are clear dead ends: find_paid_work explicitly tells agents to call start_job, which is not exposed in the toolset. Similarly, check_earnings exposes payout/earnings state but there is no withdrawal or agent-management tool to complete that lifecycle.

Resources

Need Help?