This is the mcp server of L&T
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool itself has two phases (discover/execute) but that's internal to the tool and clearly described.
With a single tool, naming is trivially consistent. The name 'discover_tools' follows a clear verb_noun pattern and accurately describes its function.
The server exposes only one tool, which feels thin for an enterprise API gateway. However, it is a meta-tool that can discover and execute numerous underlying operations, so it's not trivial; it's on the low end of acceptable.
The two-step discover-then-execute workflow allows access to any tool available through the gateway, covering the full lifecycle of querying and invoking operations. Minor gap: discovery requires a query string, so exhaustive listing may be limited without knowing the right queries.
Two-step tool finder and executor for all enterprise APIs.
STEP 1 — DISCOVER: Call with only 'query'. Returns matching tools with their names and inputSchemas.
STEP 2 — EXECUTE: Call again with 'query' + 'tool_name' + 'tool_args'. Gateway executes the tool and returns real data directly.
You NEVER call any other tool directly. Always use discover_tools.
Inputs: query (required), team, top_k, tool_args, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.