graph-tool-call
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| graph | No | Path to a pre-built tool graph JSON file (used with the 'serve' command). | |
| config | No | Path to a backends.json configuration file for aggregating multiple MCP servers (used with the 'proxy' command). | |
| source | No | URL or path to an OpenAPI/Swagger spec or MCP server tool list to ingest (used with the 'serve' command). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search for relevant tools by natural language query. |
| get_tool_schemaA | Get the full schema of a specific tool by name. |
| list_categoriesA | List all tool categories in the graph. Returns categories with their tool counts, useful for understanding the available tool landscape before searching. |
| graph_infoA | Show summary statistics about the loaded tool graph. Returns tool count, node count, edge count, and category breakdown. |
| execute_toolA | Execute an OpenAPI tool via HTTP. |
| load_sourceB | Load additional tools from an OpenAPI spec URL or file path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a distinct role: search_tools for discovery, get_tool_schema for inspection, list_categories and graph_info for overview, execute_tool for execution, and load_source for ingestion. No two tools overlap in functionality, making selection unambiguous.
Most tool names follow a consistent verb_noun snake_case pattern (search_tools, get_tool_schema, list_categories, execute_tool, load_source). The sole deviation is graph_info, which uses noun_noun instead of verb_noun, but it remains clear and stylistically consistent.
With 6 tools, the set is well-scoped for a tool-graph management server. Each tool supports a distinct step in the workflow (load, discover, inspect, execute, overview), and there is no bloat or sense of missing essentials.
The core workflow is complete: load_source brings in new tools, search_tools discovers them, get_tool_schema inspects them, and execute_tool runs them. list_categories and graph_info provide useful overview. The only minor gap is the absence of a direct 'list all tools' function, but search_tools with a broad query can cover that.