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.
| Name | Required | Description | Default |
|---|---|---|---|
| team | No | Optional department filter. | |
| query | Yes | User intent in plain natural language. | |
| top_k | No | Number of tools to return. Default 5, max 10. | |
| tool_args | No | STEP 2 only — arguments matching the tool's inputSchema exactly. | |
| tool_name | No | STEP 2 only — exact tool name from previous discover response. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does well by disclosing that this is a gateway that executes tools and returns real data, and that it requires a two-step flow. It could add a caution that executing a tool may trigger side effects depending on the underlying API, but the general execution behavior is clearly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and front-loaded: the purpose is stated first, then each step is concise and actionable. Every sentence earns its place, and the formatting makes the two-step flow easy to follow.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 5-parameter gateway with no output schema and no annotations, the description covers the full invocation flow, parameter roles, and the nature of responses. It does not cover edge cases like no matching tools or execution failures, but those are secondary to correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already explains each parameter clearly, including 'STEP 2 only' for tool_name and tool_args. The description adds step-level context but does not provide meaningful parameter details beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly identifies the tool as a 'two-step tool finder and executor' for enterprise APIs and breaks out the discover and execute steps. This leaves no ambiguity about its core purpose, and since there are no siblings, no differentiation is needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit step-by-step invocation guidance: call with only 'query' first, then call again with 'query' plus 'tool_name' and 'tool_args'. The final instruction, 'You NEVER call any other tool directly. Always use discover_tools,' gives a decisive routing rule that leaves no room for misuse.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
discover_tools2 fields changedInput schema / properties / tool_args / descriptionPrevious value: -"STEP 2 only — arguments matching the tool's inputSchema exactly. Provide together with tool_name to execute the tool."New value: +"STEP 2 only — arguments matching the tool's inputSchema exactly."Input schema / properties / tool_name / descriptionPrevious value: -"STEP 2 only — exact tool name from previous discover response. Must match a name returned in the previous discover call exactly."New value: +"STEP 2 only — exact tool name from previous discover response."discover_tools4 fields changedInput schema / properties / query / descriptionPrevious value: -"The user's intent in plain natural language."New value: +"User intent in plain natural language."Input schema / properties / tool_args / descriptionPrevious value: -"Arguments to execute the discovered tool immediately. Pass the exact arguments from the inputSchema returned in the previous discover_tools response. When provided with a single matched tool, the gateway executes it and returns real data directly."New value: +"STEP 2 only — arguments matching the tool's inputSchema exactly. Provide together with tool_name to execute the tool."Input schema / properties / tool_nameAdded value: +{
+ "description": "STEP 2 only — exact tool name from previous discover response. Must match a name returned in the previous discover call exactly.",
+ "type": "string"
+}Input schema / properties / top_k / descriptionPrevious value: -"Number of tools to return. Default 5, maximum 10."New value: +"Number of tools to return. Default 5, max 10."discover_tools3 fields changedInput schema / properties / query / descriptionPrevious value: -"The user's intent in plain natural language. Be descriptive — include the action, the subject, and any relevant context. More detail produces better matches."New value: +"The user's intent in plain natural language."Input schema / properties / team / descriptionPrevious value: -"Optional department or team filter to narrow results. Only set this if the user explicitly mentions a team or department."New value: +"Optional department filter."Input schema / properties / tool_argsAdded value: +{
+ "description": "Arguments to execute the discovered tool immediately. Pass the exact arguments from the inputSchema returned in the previous discover_tools response. When provided with a single matched tool, the gateway executes it and returns real data directly.",
+ "type": "object"
+}cprs_getpurchasetypescprsorm_getjobbasedwhlistcreate_api_invoice_fetchtaxdetailscreate_api_invoice_fetchworkflowstatuscreate_api_invoice_postinvactionlistcreate_api_invoice_postinvoicemomsubmitpostInvActionListsend_mailcprs_getpurchasetypescprsorm_getjobbasedwhlistcreate_api_invoice_fetchtaxdetailscreate_api_invoice_fetchworkflowstatuscreate_api_invoice_postinvactionlistcreate_api_invoice_postinvoicemomsubmitpostInvActionListsend_mailadvancesearchjobdetailscode_execution_guidecprs_getpurchasetypescprsorm_getjobbasedwhlistcreate_cc_ext_docdownload_getfilecontentasbytediscover_toolsget_current_weatherget_diesel_consumptionget_invoice_statushow_to_send_lnt_emaillistbloblnt_email_brand_guidelineslnt_invoice_formatpublic_quotessend_formatted_email_guideSQL_EXECUTIONweekly_project_update_pptadvancesearchjobdetailscode_execution_guide2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]cprs_getpurchasetypes3 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / properties / request_body / descriptionPrevious value: -"Request body imported from cURL. Content-Type: application/json. Template/example: {"New value: +"Request body imported from cURL. Example: {\n \"intUID\": 1207,\n \"intCompanyCode\": 1,\n \"chrActiveStatus\": \"Y\"\n}"Input schema / properties / request_body / typeAdded value: +"object"cprs_requisition_workflowcprsorm_getjobbasedwhlist3 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / properties / request_body / descriptionPrevious value: -"Request body imported from cURL. Content-Type: application/json. Template/example: {"New value: +"Request body imported from cURL. Example: {\n \"strJobcode\": \"LE20M143\",\n \"intCompanyCode\": 1,\n \"isWarehouseLinkedOtherjob\": \"N\"\n}"Input schema / properties / request_body / typeAdded value: +"object"create_api_invoice_fetchtaxdetailscreate_api_invoice_fetchworkflowstatuscreate_api_invoice_postinvactionlistcreate_api_invoice_postinvoicemomsubmitcreate_cc_ext_docdownload_getfilecontentasbyteexecute_codeget_current_weatherget_diesel_consumptionget_invoice_statushow_to_send_lnt_email2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]listbloblnt_email_brand_guidelines2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]lnt_invoice_format2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]postInvActionListpublic_quotessend_formatted_email_guide2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]send_invoice_email_guidesend_mailSQL_EXECUTIONweekly_project_update_ppt2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / requiredAdded value: +[]weekly_project_update_pptexecute_codecode_execution_guidecreate_api_invoice_fetchtaxdetailscreate_api_invoice_fetchworkflowstatuscreate_api_invoice_postinvactionlistcreate_api_invoice_postinvoicemomsubmit
Add one secure layer between your agents and this server.