interpro-mcp-server

InterPro clan metadata and members

interpro_get_clan

Read-onlyIdempotent

Retrieve a Pfam, CDD, or PIRSF clan/set and a cursor page of member entries; optionally include its relationship graph, returned in slices that fit the response budget and paged with relationshipOffset.

Input Schema

Name	Required	Description
`limit`	No	Positive integer member page size; values above 100 are clamped to 100 with a notice; defaults to 20.
`cursor`	No	Opaque nextCursor with unchanged accession, sourceDatabase, and includeRelationships; limit, relationshipOffset, and includeThumbnail may change.
`accession`	Yes	Set accession, such as CL0016 (Pfam), cl21453 (CDD), or PIRSF000047; no URL syntax.
`sourceDatabase`	No	Inferred from uppercase CL (Pfam), lowercase cl (CDD), or PIRSF; supply explicitly for mixed-case CL prefixes.
`includeThumbnail`	No	Include each Wikipedia thumbnail image, base64 data often tens of KB; defaults to false.
`relationshipOffset`	No	Position of the first relationship item to return, counting nodes, then links; defaults to 0. A value above 0 requires includeRelationships: true; pass relationshipsPage.nextOffset to continue.
`includeRelationships`	No	Include the relationship graph, one slice per call that fits the response budget; defaults to false.

Output Schema

Name	Required	Description
`cap`	No	Effective member page size after clamping.
`url`	No	Canonical InterPro clan website URL.
`clan`	No	Complete metadata, with relationships and Wikipedia thumbnails omitted unless requested; requested relationships hold the slice relationshipsPage locates.
`page`	No	Member continuation and total.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Members returned in this page.
`notice`	No	Next relationship slice call, omitted relationships or thumbnails, or empty-page guidance.
`members`	No	Complete upstream member records.
`accession`	No	Canonical requested clan accession.
`sourceUrl`	No	Official clan metadata API source URL.
`truncated`	No	More members remain.
`totalCount`	No	Total matching members.
`effectiveQuery`	No	Applied canonical target, relationship, and thumbnail selection.
`sourceDatabase`	No	Set database.
`relationshipsPage`	No	Position and totals of the relationship slice; present only when includeRelationships is true.
`relationshipsIncluded`	No	Whether relationship projection was requested.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, open-world behavior. The description adds useful behavioral context beyond them: pagination via cursor, optional relationship-graph inclusion, response-budget slicing, and relationshipOffset paging.

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?

It is a single front-loaded sentence with no wasted text. The primary operation comes first, and the optional relationship-graph behavior is appended efficiently.

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?

With a rich input schema, an output schema, and annotations covering safety, the description is complete enough for correct invocation. The remaining details, such as limit clamping and sourceDatabase inference, are adequately handled by the schema rather than the description.

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 the parameter documentation already carries the detail. The description reinforces cursor paging and relationshipOffset but does not add much beyond what the schema already explains for limit, sourceDatabase, includeThumbnail, and includeRelationships.

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 gives a specific verb and resource: retrieve a Pfam, CDD, or PIRSF clan/set plus a cursor page of member entries. That clan/set focus makes it distinguishable from the entry-, protein-, and search-oriented sibling tools without needing to name them.

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 use case is implied clearly enough: use this when you need clan/set metadata and members. However, it does not explicitly say when to choose this over interpro_get_entry, interpro_search_entries, or other siblings, nor does it state any exclusions.

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

All interpro-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.