Skip to main content
Glama

Polymer Entity

polymer_entity
Read-onlyIdempotent

"Chain [N] of PDB [ID]" / "sequence of chain in [pdb_id]", fetch the polymer-entity (protein/DNA/RNA chain) metadata for a specific PDB entry. Returns sequence, source organism, UniProt cross-references, GO annotations. Use to drill into one chain of a multi-chain structure.

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": {
      "pdb_id": "1abc",
      "entity_id": "1"
    },
    "name": "polymer_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdb_idYes
entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the content of the response (sequence, organism, cross-references, GO terms), which is partly redundant given an output schema exists, and says nothing about error behavior when an entity_id does not exist or about chain-vs-entity numbering.

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 core sentence about fetching polymer-entity metadata and its return contents is efficient and front-loadable, but the leading pair of quoted user-query fragments is noisy and interrupts the structure. Removing or integrating them would sharpen the definition without losing information.

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?

For a two-parameter read-only lookup with an output schema and full annotations, the description covers purpose, return contents, and a usage cue, which is close to sufficient. The remaining gap is the chain-versus-entity identifier ambiguity, which matters for correct invocation on multi-chain entries.

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 coverage is 0%, so the description must compensate, and it partially does: the quoted patterns "Chain [N] of PDB [ID]" and "sequence of chain in [pdb_id]" map pdb_id to a PDB ID and entity_id to a chain index. However, this conflates polymer entity IDs with chain IDs, which are distinct concepts in PDB data, leaving the semantics of entity_id ambiguous rather than clarified.

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

Purpose4/5

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

The description states a specific verb and resource: fetch polymer-entity metadata (protein/DNA/RNA chain) for a specific PDB entry, and lists the payload (sequence, source organism, UniProt cross-references, GO annotations). It does not name or differentiate itself from close siblings such as entity_profile or rcsb_pdb_structure, so an agent must infer the boundary.

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?

"Use to drill into one chain of a multi-chain structure" gives a usage context, but there are no exclusions and no named alternatives among the several structurally similar siblings (entity_profile, resolve_entity, rcsb_pdb_structure). The leading quoted example queries hint at intent rather than stating routing rules.

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.