nullary

search_peptide_stability_issues

Read-onlyIdempotent

Peptide stability/half-life 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

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond the topic, but it does not contradict the annotations. However, it does not disclose pagination, filtering behavior, or what 'failures' means in terms of data structure, so credit is limited.

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 short—essentially a noun phrase—which is concise but under-specified. It does not 'earn its place' by adding information beyond the tool name; it merely reinforces the topic. While there is no verbosity, the minimalism reduces usefulness.

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?

With numerous sibling tools covering similar domains (e.g., search_failed_peptide_therapeutics), the description is not complete enough to understand this tool's unique scope. The output schema exists, but the description fails to clarify whether results are limited to stability/half-life failures or how this differs from broader failure searches. This is a critical gap for tool selection.

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?

All 6 parameters are fully described in the schema (100% coverage), so the description does not need to elaborate on them. The schema already explains tier, limit, offset, target, outcome, and compound. The description adds no parameter-specific meaning, but the comprehensive schema covers this dimension.

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

Purpose3/5

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

The description 'Peptide stability/half-life failures' gives a general topic but lacks an explicit verb (e.g., 'Search for' or 'List'), and it does not distinguish this tool from closely related siblings like search_failed_peptide_therapeutics. It is more than a pure tautology because it specifies the subject area, but the purpose is vague without the name providing the action.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or compare with other search tools, especially the similar search_failed_peptide_therapeutics. This is a clear gap given the abundance of sibling search tools.

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?