A
licenseNot graded
qualityA
maintenanceConverts a GraphQL schema into MCP tools, allowing AI to discover and call GraphQL queries and mutations via natural language.
34 npm
MIT
VectorSmith
by kjgpta
Related Servers
Alternatives to VectorSmith
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceTransforms OpenAPI definitions into MCP tools for seamless LLM-API integration.89 npm1MIT
- AlicenseNot gradedqualityBmaintenanceExposes Iceberg-backed ontology objects, links, and actions as typed MCP tools for LLM agents, enabling governed data access and operations without raw SQL.MIT
- AlicenseAqualityDmaintenanceEnables AI-powered generation of production-ready CTP (ConveniencePro Tool Protocol) tools from natural language descriptions, including tool definitions, implementations, tests, and TypeScript validation.58 npmMIT
- FlicenseNot gradedqualityDmaintenanceAggregates tools from multiple MCP servers, generates TypeScript definitions, and executes custom TypeScript scripts to orchestrate cross-server tool calls.-
- AlicenseNot gradedqualityAmaintenanceEnables LLM clients to select the most relevant MCP tools from a catalog within a context-token budget, without executing them or shipping keys.1MIT
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation3/5
get_invoice, count_invoices, and the meta discovery/execution tools are distinct, though run_tool is a catch-all that could execute any of the invoice tools. The real ambiguity is that search_invoices already supports status filtering, making search_paid_invoices and list_overdue_invoices overlapping subsets. The use-when guidance helps, but an agent could reasonably pick either general or specialized tools for paid/overdue queries.
Naming Consistency5/5
All tool names follow a predictable snake_case verb_noun pattern: search_invoices, get_invoice, count_invoices, list_overdue_invoices, search_paid_invoices, run_tool, and list_available_tools. The meta tools do not break the convention, so naming is consistent across the set.
Tool Count5/5
Seven tools is well within the ideal scope, with two infrastructure tools for dynamic discovery/execution and five read-only invoice tools. Each tool has a reasonable purpose, and the count does not feel bloated or thin.
Completeness4/5
The read-only invoice workflow is well covered: search, get by ID, count, overdue list, and paid search. It lacks create/update/delete operations and an explicit 'list all invoices' tool, but search with filters can work around the latter, and the descriptions imply a query/reporting focus.
Maintenance
ActivityMaintained
ResponsivenessResponsive