Skip to main content
Glama

legume_family

Read-onlyIdempotent

Members of an LIS legume gene family across chickpea, lentil, pea, soybean and Medicago truncatula. gene: a chickpea/lentil/pea/Medicago gene ID, a soybean Ensembl ID (GLYMA_01G000600) or LIS name (Glyma.01G000600), or a family ID (Legume.fam3.00142). Use it to go from a soybean or pea gene (e.g. from orthologues or expression results) to its chickpea and lentil relatives, or back. Families are broader than orthologue groups. dataset (e.g. 'chickpea_desi' or 'chickpea_kabuli_v1') picks one when a Ca_ ID exists in several annotations.

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": {
      "gene": "<gene>"
    },
    "name": "legume_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
datasetNo
per_speciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description contributes real behavioral detail beyond them: which gene identifier formats are accepted and the ambiguity rule that 'dataset' resolves Ca_ IDs found in several annotations. It does not describe result volume or ordering, and per_species behavior is unstated.

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 text is dense and front-loaded, starting with what a family is before the identifier formats and the use case. It is somewhat long for one paragraph and the 'gene:' label reads like a schema footnote, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the agent should be told what the result looks like; the description only implies a membership list and says nothing about shape, size limits, or how per_species truncates results. For a three-parameter lookup tool with zero schema coverage, one undocumented parameter and an unexplained return shape leave a real gap.

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 0%, so the description must carry all parameter meaning. It does this well for 'gene' (three accepted ID formats with an example of each) and for 'dataset' (example values and the disambiguation rule), but 'per_species' is never mentioned, so one of three parameters remains opaque.

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 names a specific resource (members of an LIS legume gene family) and pins down its scope across five species. It also distinguishes the tool from a conceptual sibling by stating 'Families are broader than orthologue groups', so an agent can separate this from the orthologues tool without opening either schema.

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 concrete use case: go from a soybean or pea gene (e.g. from orthologues or expression results) to chickpea and lentil relatives, or the reverse. That is clear context, but there is no explicit when-not-to-use rule beyond the implicit contrast with orthologue groups.

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