Skip to main content
Glama
Sign In
propaths-mcp

propaths-mcp

by Tahsin-Kazi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_pathway

Read-onlyIdempotent

Retrieve a specific pathway by ID, including its node, ancestors, children, and interactions. Provides a pathway-first view into the interaction graph.

Instructions

A single pathway by id: the node, its ancestors and children, and the interactions placed in it. The pathway-first way into the graph.

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": {
      "pathway_id": "<pathway_id>"
    },
    "name": "get_pathway"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathway_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the tool read-only and idempotent. The description adds valuable behavioral context by specifying the exact data composition (node, ancestors, children, interactions), which helps the agent understand the response shape. No contradiction detected.

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?

The description is a single, concise sentence that front-loads the core purpose and then details the scope. Every phrase earns its place with no redundancy.

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?

Given the read-only annotation and the straightforward single-ID lookup, the description adequately conveys what is returned. It omits error handling or not-found behavior, but for this simple tool the provided information is largely sufficient.

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

Parameters2/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 compensate, but it only says 'by id' which adds little beyond the parameter name 'pathway_id'. There is no explanation of the ID format, source, or any constraints, leaving the agent with minimal guidance.

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 clearly states the tool retrieves a single pathway by ID and enumerates what is returned (node, ancestors, children, interactions). This is specific and action-oriented, and the 'pathway-first' phrase helps position it among other graph access tools.

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 description implies this is the primary entry point when starting from a pathway, but it does not explicitly mention alternatives or conditions for when not to use it. The sibling get_pathway_tree is likely a related option, yet no routing guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools