STRING Database MCP Server

STRING: Resolves protein identifiers to metadata

string_resolve_proteins

Maps one or more protein identifiers to their corresponding STRING metadata, including: gene symbol, description, sequence, domains, species, and internal STRING ID.

This method is useful for translating raw identifiers into readable, annotated protein entries.

Example input: "TP53%0dSMO"

Input Schema

TableJSON Schema

Name	Required	Description
`species`	No	NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).
`proteins`	Yes	One or more input protein identifiers (gene symbols, UniProt IDs, etc.), separated by carriage return (%0d).
`show_sequence`	No	Include sequences. Use only if the user requests sequence data.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 30, 2026

changedInput schema / properties / show_sequence / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "enum": [
-          "0",
-          "1"
-        ],
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "description": "Include sequences. Use only if the user requests sequence data.",
-    "examples": [
-      "0",
-      "1"
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "0",
+      "1"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / show_sequence / description

Added value: +"Include sequences. Use only if the user requests sequence data."

addedInput schema / properties / show_sequence / examples
```
Added value: +[
+  "0",
+  "1"
+]
```

removedInput schema / properties / species / anyOf

Removed value: -[
-  {
-    "description": "NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / species / description

Added value: +"NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes)."

addedInput schema / properties / species / type
```
Added value: +"string"
```

Changed4 schema fields changedSep 29, 2026

changedInput schema / properties / proteins / description

Previous value: -"Required. One or more input protein identifiers (gene symbols, UniProt IDs, etc.), separated by carriage return (%0d). Example: TP53%0dSMO"New value: +"One or more input protein identifiers (gene symbols, UniProt IDs, etc.), separated by carriage return (%0d)."

addedInput schema / properties / proteins / examples
```
Added value: +[
+  "TP53%0dSMO"
+]
```

changedInput schema / properties / show_sequence / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "enum": [
-          "0",
-          "1"
-        ],
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "description": "Optional. Include sequences when set to 1. Use only if the user requests sequence data."
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "enum": [
+          "0",
+          "1"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "Include sequences. Use only if the user requests sequence data.",
+    "examples": [
+      "0",
+      "1"
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / species / anyOf

Previous value: -[
-  {
-    "description": "Optional. NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the output content (metadata fields) and includes an input example, but it does not explicitly state that the operation is read-only, whether it has rate limits, or any authentication requirements. The gaps are moderate for a query tool.

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?

The description is short, front-loaded, and structured into three brief sentences. The example input duplicates a schema example slightly, but overall it is efficient and easy to parse.

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?

Given the tool's moderate complexity, full schema description coverage, and the presence of an output schema, the description is nearly complete for selection and invocation. It lacks explicit sibling differentiation, but the purpose and return metadata are sufficiently described.

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 input schema already documents all three parameters in detail. The description only restates that one or more protein identifiers are accepted and gives an example that duplicates the schema example. It adds no meaningful parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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: 'Maps one or more protein identifiers to their corresponding STRING metadata.' It also enumerates the metadata types returned, making the tool's purpose clear. However, it does not explicitly differentiate itself from sibling tools such as string_sequence_search or string_functional_annotation.

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

Usage Guidelines4/5

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

The description provides clear usage context: 'useful for translating raw identifiers into readable, annotated protein entries.' This tells an agent when the tool is appropriate. It does not, however, mention when not to use it or name alternative sibling tools for overlapping tasks.

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

All STRING Database 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.