nullary

search_ancestry_specific_failures

Read-onlyIdempotent

Ancestry-specific CRISPR failures.

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

D1.8/5.0

Behavior1/5

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

The description adds no behavioral context beyond the annotations. While annotations already declare readOnlyHint=true and destructiveHint=false, the description does not explain how the tool behaves (e.g., default tier, filtering semantics, what 'curated' vs 'all' means) or any limitations, making the agent rely solely on schema fields.

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

Conciseness2/5

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

The description is a single under-specified sentence. It is not a case of conciseness but rather of inadequacy; no important information is front-loaded, and the description fails to earn its place by providing any actionable detail.

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 has six parameters and an output schema, the description should clarify what 'ancestry-specific CRISPR failures' means and how it overlaps or differs from sibling tools like search_failed_guides or search_failed_essentiality_screens. It does not, leaving the agent with insufficient context for effective 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 all six parameters are well-documented in the input schema itself. The description adds no additional parameter meaning, but the baseline of 3 is appropriate because the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Ancestry-specific CRISPR failures.' is a noun phrase that essentially restates the tool name with the addition of 'CRISPR'. It lacks a verb (e.g., 'Search', 'List') and does not clarify the scope or distinguish it from sibling search_failure tools beyond the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the many sibling search_* tools. No context about typical use cases, exclusions, or alternatives is provided, leaving the agent to infer applicability from the name alone.

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?