Per-target Layer-1 model card: training counts and held-out scaffold-split metrics (ROC-AUC, PR-AUC, Brier, calibration). Accepts a gene symbol (e.g. EGFR) or UniProt accession (e.g. P00533).
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | gene symbol or UniProt accession (required) |
| Name | Required | Description | Default |
|---|---|---|---|
| query_metadata | Yes | Echo of the resolved query. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Per-target Layer-1 model card: training counts and held-out scaffold-split metrics.",
+ "properties": {
+ "query_metadata": {
+ "description": "Echo of the resolved query.",
+ "type": "object"
+ }
+ },
+ "required": [
+ "query_metadata"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds meaningful context about the output contents (training counts, metrics, calibration) and input formats, which goes beyond the structured annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose ('Per-target Layer-1 model card'), and includes essential details without redundancies. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single parameter and an output schema (present), the description adequately covers the tool's behavior and return value semantics. It lacks explicit edge-case handling (e.g., invalid target), but the output schema and simple getter nature make this sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the parameter is fully documented. The description adds concrete examples (EGFR, P00533) and clarifies the two accepted identifier formats, which assists correct invocation beyond the schema's generic 'gene symbol or UniProt accession'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as retrieving a per-target Layer-1 model card with specific metrics (ROC-AUC, PR-AUC, Brier, calibration). It names the resource ('model card') and distinguishes it from sibling tools like get_coverage or get_target_landscape, which serve different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use the tool (to fetch model card for a target) and specifies accepted input formats (gene symbol or UniProt accession) with examples. It does not explicitly compare with alternatives or state exclusions, but the intended use is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.