Skip to main content
Glama

Catnap Antibody Info

catnap_antibody_info
Read-onlyIdempotent

Metadata for an HIV antibody in LANL CATNAP: which region of the virus it binds (CD4 binding site, V3 glycan, MPER, ...), its aliases, the paper that isolated it with PubMed id, light chain type, ADCC activity, and its mean panel IC50 with the number of viruses tested. Answers "what does PGT121 bind", "who isolated 10-1074", "how broad is this antibody's panel". For the per-strain measurements behind that panel, use catnap_search_neutralization.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "10-1074"
    },
    "name": "catnap_antibody_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAntibody name or alias, substring match, e.g. "VRC01", "PGT121".
limitNoMaximum antibodies to return (default 10, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds substantive behavior: it lists the exact metadata fields returned and clarifies that panel breadth is summarized as a mean IC50 over N viruses rather than raw measurements. It does not mention result truncation or the 50-result cap, which is the main remaining gap.

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

Conciseness4/5

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

Front-loaded with the resource and its returned fields, then example questions, then an explicit routing sentence to the sibling. The field enumeration is long but each item is informative for an agent deciding whether this tool answers its question; no filler sentences.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so thoroughly by naming each metadata field. Only two simple parameters, both documented in schema, and the alternative is named, so nothing essential for correct invocation is missing.

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 both parameters (name, limit) are already documented with examples and defaults. The description adds no additional syntax or matching semantics beyond what the schema states, so baseline 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?

States a specific resource (HIV antibody metadata in LANL CATNAP) and enumerates exactly what is returned: binding region, aliases, isolation paper with PubMed id, light chain type, ADCC activity, mean panel IC50 with virus count. It also explicitly differentiates from the sibling by naming catnap_search_neutralization for per-strain data.

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

Usage Guidelines5/5

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

Gives concrete triggering questions ("what does PGT121 bind", "who isolated 10-1074", "how broad is this antibody's panel") and names the alternative tool plus the condition that selects it (per-strain measurements). Both when-to-use and when-to-use-something-else are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.