nullary

search_failed_adcs

Read-onlyIdempotent

ADCs that failed at any stage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No	Confidence tier. 'curated' (default) returns the credible layer; 'all' also includes high-volume screening-grade rows (PubChem HTS inactives, CRISPR non-essential tails).	curated
`limit`	No	Maximum number of findings to return (1–100, default 25).
`offset`	No	Number of findings to skip before this page, for pagination (default 0).
`target`	No	UniProt accession or gene symbol
`outcome`	No	outcome filter (inactive, failed_safety, terminated, …)
`compound`	No	compound name, ChEMBL ID, or InChIKey

Output Schema

TableJSON Schema

Name	Required	Description
`findings`	No	Matching negative findings (same shape as the REST /findings endpoint).
`has_more`	No	True when more results exist beyond this page.
`coverage_note`	No	Honest coverage caveat for thin Phase-1 modalities (present only when relevant).
`query_metadata`	Yes	Echo of the resolved query — tool, limit, offset, and any applied presets.
`returned_count`	No	Findings returned in this page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedMay 25, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of findings to return (1–100, default 25)."

addedInput schema / properties / offset / description

Added value: +"Number of findings to skip before this page, for pagination (default 0)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "coverage_note": {
+      "description": "Honest coverage caveat for thin Phase-1 modalities (present only when relevant).",
+      "type": "string"
+    },
+    "findings": {
+      "description": "Matching negative findings (same shape as the REST /findings endpoint).",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "description": "True when more results exist beyond this page.",
+      "type": "boolean"
+    },
+    "query_metadata": {
+      "description": "Echo of the resolved query — tool, limit, offset, and any applied presets.",
+      "type": "object"
+    },
+    "returned_count": {
+      "description": "Findings returned in this page.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "query_metadata"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds the scope 'at any stage', which is a useful behavioral trait beyond annotations, but it does not explain how failures are defined or what stages are covered. It does not contradict annotations.

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

Conciseness3/5

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

The description is extremely concise (four words) and front-loaded, but it is a sentence fragment that lacks structure. While efficient, it is too sparse to serve as a fully effective description for a tool with multiple parameters and many sibling alternatives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, many sibling tools, output schema), the description is incomplete. It omits context about what 'failed' includes, the role of the tier parameter, and how it relates to other failure search tools. The output schema covers return values, but the description fails to provide sufficient operational context.

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 coverage is 100%, so the input schema fully documents all six parameters. The description itself does not mention parameters or add semantics beyond the schema, warranting the baseline score of 3.

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 'ADCs that failed at any stage' clearly identifies the resource (ADCs) and the specific criterion (failed at any stage), which is more than a tautology. It differentiates from sibling tools by focusing specifically on ADCs, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus sibling tools such as search_failed_clinical_antibodies or search_inactive_compounds. The description offers no context for choosing this tool, leaving the agent to infer usage solely from the name.

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

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

Resources

Need Help?