nullary

search_indication_history

Read-onlyIdempotent

ALL failed approaches for an indication 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).
`indication`	Yes	indication (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

A3.7/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. The description adds the scope of 'ALL failed approaches' but does not disclose the default tier='curated' behavior, which may not return literally all rows, nor does it mention pagination or completeness caveats. Since annotations carry the safety profile, this is acceptable but not enhanced.

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, front-loaded with 'ALL', and contains no wasted words. It fully captures the essential purpose and scope in minimal space.

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

Completeness3/5

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

The description is very brief and does not provide explicit usage guidance (e.g., when to use vs modality-specific siblings) or directly mention the tier distinction. Although the rich schema and annotations cover parameters and safety, additional context about the curated/all distinction and sibling alternatives would improve completeness for an agent.

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 provides 100% coverage with descriptions for all four parameters including tier's confidence-tier semantics and limit/offset pagination. The description adds no additional parameter meaning, so the baseline score 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 clearly states the tool returns all failed approaches for a given indication across all modalities, with the specific verb 'search' implied by the name. It distinguishes from modality-specific sibling tools like search_failed_adcs and search_failed_bispecifics by covering 'every modality'.

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

Usage Guidelines3/5

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

The description implies comprehensive cross-modality use via 'ALL' and 'every modality', but it does not explicitly state when to choose this tool over a modality-specific sibling or mention the tier parameter that lets users choose 'curated' vs 'all'. It lacks explicit alternatives or exclusions.

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?