Skip to main content
Glama

Feature Summary

feature_summary
Read-onlyIdempotent

"Domain map of [protein]" / "annotated features of [accession]" / "what regions / sites does [protein] have", annotated features (domains, active sites, transmembrane regions, mutagenesis sites, glycosylation, disulfide bonds, etc.) for a UniProt accession. Use for structural/functional analysis without pulling the full protein record.

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": {
      "accession": "P38398"
    },
    "name": "feature_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessionYes

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of annotated features
by_typeYesFeature count by type
accessionYesUniProt accession

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 scope context by enumerating what kinds of annotations come back and that it is a lightweight alternative to a full record fetch, but it does not mention coverage/completeness of annotations or rate/response characteristics.

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 content is compact: a set of quoted trigger phrasings followed by one explanatory sentence. The quoted query fragments are slightly noisy for a tool description but function as front-loaded retrieval cues, and nothing is redundant.

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 annotations covering safety, an output schema present, and only one required parameter, the definition supplies everything needed to decide and invoke correctly. The remaining gap is minor: no explicit statement of what happens with an invalid or non-UniProt accession.

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?

The single parameter is named only 'accession' in the schema with 0% description coverage, so the description's phrase "for a UniProt accession" is doing real disambiguation work (UniProt vs. any other accession namespace). That is the only added meaning; no format or validation guidance is offered.

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 resource (annotated features) for a specific entity type (a UniProt accession) and enumerates the feature classes returned (domains, active sites, transmembrane regions, mutagenesis sites, glycosylation, disulfide bonds). It is clearly distinct from the search-oriented siblings like proteomes_search, though it names no alternative explicitly.

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?

It gives a clear use case ("structural/functional analysis") and an implicit boundary ("without pulling the full protein record"), which effectively tells the agent to prefer this over a full-record retrieval. It stops short of explicit when-not-to-use conditions or a named alternative tool.

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.