Skip to main content
Glama

Keyword

keyword
Read-onlyIdempotent

"UniProt keyword KW-N info" / "what does keyword [X] mean", fetch a UniProt controlled-vocabulary keyword by ID. Use to look up annotation tags like "Kinase" / "Membrane" / "Disease-associated".

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": {
      "keyword_id": "KW-0002"
    },
    "name": "keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyword_idYes

Output Schema

NameRequiredDescriptionDefault
idNoKeyword ID (e.g. KW-0007)
nameNoKeyword name
categoryNoKeyword category
synonymsNoAlternative keyword names
definitionNoKeyword definition

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / category / properties
      Added value: +{
      +  "id": {
      +    "type": "string"
      +  },
      +  "name": {
      +    "type": "string"
      +  }
      +}
    • changedOutput schema / properties / category / type
      Previous value: -"string"New value: +"object"
  2. 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, non-destructive, and openWorldHint, so the safety profile is covered. The description adds that this is a controlled-vocabulary lookup rather than free-text search, but says nothing about lookup failures, coverage, or result scope beyond what the existing output schema would carry.

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 definition is two compact sentences that front-load the example phrasings an agent might see. It is efficient, though the heavy quoting is slightly noisy compared to a plain statement of purpose.

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 single-parameter, read-only, idempotent lookup with an output schema and full annotation coverage, the description supplies enough to call it correctly. The remaining gap is the ID-versus-name ambiguity for the one required parameter.

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; it partially does by signaling the 'KW-N' identifier shape and referencing keyword tags. However, quoting queries like 'what does keyword [X] mean' alongside tag names such as 'Kinase' leaves it ambiguous whether keyword_id accepts only canonical IDs or also plain names.

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 a UniProt controlled-vocabulary keyword by ID,' and illustrates it with concrete keyword tags like 'Kinase' and 'Membrane.' It does not explicitly distinguish itself from the only related sibling (proteomes_search), so it falls short of a 5.

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 provides real usage framing by quoting the intents it serves ('what does keyword [X] mean') and saying to 'use to look up annotation tags.' There is no explicit when-not guidance or named alternative, which keeps it below a 5.

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.