Skip to main content
Glama

gene_function

Read-onlyIdempotent

IWGSC RefSeq v2.1 functional annotation (InterPro, Pfam, Gene Ontology) for a gene symbol or any-version IWGSC ID. annotation_types filters e.g. ['Gene Ontology'] or ['Pfam','InterPro'].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "gene_function"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes
annotation_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered by structured data. The description adds real behavioral context by pinning the annotation source to RefSeq v2.1 and disclosing that filtering is by annotation type. It says nothing about what happens for an unknown gene or what an empty result means.

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?

Two compact sentences with no filler; the source, accepted identifiers, and filter options are all front-loaded in the order an agent needs them.

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 tool with no output schema, the description covers source, accepted identifier formats, and filter values adequately. The remaining gap is return-shape/empty-result behavior, which is minor given the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter meaning and it largely does: identifier accepts a gene symbol or any-version IWGSC ID, and annotation_types is illustrated with concrete values like ['Gene Ontology'] and ['Pfam','InterPro']. It does not state whether annotation_types is case-sensitive or what the default returns when omitted.

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?

States a concrete resource (IWGSC RefSeq v2.1 functional annotation via InterPro, Pfam, Gene Ontology) and the accepted input forms, so an agent knows what it retrieves. It stops short of naming a sibling such as gene_pathways, so the boundary between 'GO annotation' and 'pathways' is left to inference.

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?

Usage is implied by the described inputs and filter examples, but there is no explicit when-to-use or when-not-to-use guidance relative to gene_pathways, gene_expression, or resolve_gene. The note that any IWGSC ID version is accepted is helpful context but not routing guidance.

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.

Resources