nullary

search_target_history

Read-onlyIdempotent

ALL failed approaches against a target across every modality.

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`	Yes	UniProt accession or gene symbol (required)

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

A4/5.0

Behavior3/5

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

The description discloses that only 'failed approaches' are returned and that the scope spans 'every modality', which is useful context beyond the readOnlyHint and idempotentHint annotations. However, it makes a strong 'ALL' claim that sits somewhat uneasily with the openWorldHint annotation, though not enough to be a contradiction. No additional behavioral traits (e.g., result ordering, data curation caveats) are disclosed.

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 sentence that immediately conveys the core function and scope. It is front-loaded and every word contributes meaning, with no redundancy or filler.

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?

The description, combined with the comprehensive input schema and annotations, gives an agent enough context to invoke the tool correctly. The output schema is present, so return-value details do not need to be in the description. While the description is minimal, it fully captures the essential behavior, though slightly more clarity on what 'every modality' includes would be helpful given the large sibling family.

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%: all four parameters (target, tier, limit, offset) have detailed descriptions in the input schema, including tier behavior for 'curated' vs 'all'. The tool description adds no parameter-level information beyond what the schema already provides, so the baseline of 3 applies.

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 clearly states the tool returns 'ALL failed approaches against a target across every modality', specifying both the resource (failed approaches) and the scope (any target, every modality). This effectively distinguishes it from the many modality-specific search_failed_* sibling tools, making the purpose unmistakable.

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

Usage Guidelines4/5

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

The phrase 'across every modality' implicitly establishes this as the cross-modality aggregate search tool, contrasting with sibling tools that target specific modalities. While it doesn't explicitly name alternatives, the context is clear enough for an agent to infer when to use this tool over modality-specific ones.

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?