Skip to main content
Glama

Pathways For Entity

pathways_for_entity
Read-onlyIdempotent

Pathways containing an entity, looked up by external resource id (e.g. UniProt accession).

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": {
      "entity_id": "P04637"
    },
    "name": "pathways_for_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
speciesNoNCBI taxonomy id as a string (default "9606", human).
resourceNoUniProt | ChEBI | Ensembl | NCBI | GeneCards | ... (default UniProt)
entity_idYesIdentifier within the resource, e.g. "P04637" for TP53.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesPathways containing the specified entity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / resource / description
      Previous value: -"UniProt | ChEBI | Ensembl | NCBI | GeneCards | … (default UniProt)"New value: +"UniProt | ChEBI | Ensembl | NCBI | GeneCards | ... (default UniProt)"
    • changedInput schema / properties / species / description
      Previous value: -"NCBI taxonomy id as a string (default \"9606\" — human)."New value: +"NCBI taxonomy id as a string (default \"9606\", human)."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "entity_id": "P04637"
      +  },
      +  {
      +    "entity_id": "CHEBI:15377",
      +    "resource": "ChEBI",
      +    "species": "9606"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of items returned.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "Pathways containing the specified entity",
      +      "items": {
      +        "properties": {
      +          "className": {
      +            "description": "Type (usually Pathway)",
      +            "type": "string"
      +          },
      +          "dbId": {
      +            "description": "Internal database ID",
      +            "type": "number"
      +          },
      +          "displayName": {
      +            "description": "Pathway name",
      +            "type": "string"
      +          },
      +          "schemaClass": {
      +            "description": "Schema class",
      +            "type": "string"
      +          },
      +          "species": {
      +            "properties": {
      +              "dbId": {
      +                "type": "number"
      +              },
      +              "displayName": {
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "stableId": {
      +            "description": "Stable identifier",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

B3.4/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. The description adds that the lookup hinges on an external identifier namespace (UniProt/ChEBI/etc.), which affects result fidelity, but says nothing about coverage, limits, or empty-result behavior. An output schema exists, so return shape need not be described.

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?

A single front-loaded sentence with no filler; the identifying condition (external resource id) follows the purpose immediately. It is tightly written but so terse that it forgoes room for the routing context an agent would benefit from.

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?

With a full schema, an output schema, and rich annotations, the description's remaining burden is mostly disambiguation from pathway/reactome/entity siblings, which it does not provide. It is adequate to call the tool correctly but thin for choosing it.

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% and the schema already carries per-parameter descriptions plus two examples, so the baseline is 3. The description reinforces that entity_id belongs to an external resource namespace and gives the UniProt accession case, but adds no syntax or resource-specific formatting rules beyond the schema.

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?

"Pathways containing an entity" states a specific resource and relation, and "looked up by external resource id (e.g. UniProt accession)" pins down the query key. An agent can distinguish it from a generic pathway fetch, though it does not name a sibling to route against.

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?

The phrase "looked up by external resource id" implies the precondition for use (you must have an external accession, not an internal id or free-text name), but there is no explicit when-not guidance and no alternative named for symbol/name-based lookups. Usage is inferable rather than stated.

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.