MCP Sankhya Community Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| execute_queryA | Execute read-only SQL query (SELECT and EXPLAIN PLAN only). CTEs (WITH ... SELECT) accepted. Use list_schemas to see available connections and their readonly status. |
| insert_queryA | Insert a single row into a table. Commits automatically. Only available on writable connections (readonly=false in list_schemas). Returns the number of rows inserted. |
| update_queryA | Execute an UPDATE statement. Commits automatically. Only available on writable connections (readonly=false in list_schemas). Returns the number of rows updated. |
| delete_queryA | Execute a DELETE statement. Commits automatically. Only available on writable connections (readonly=false in list_schemas). Returns the number of rows deleted. |
| call_procedureA | Call a stored procedure or package procedure via anonymous PL/SQL block. Supports IN parameters only; OUT parameters are not supported. Commits automatically. Only available on writable connections. |
| create_triggerA | Create or replace a trigger using a full DDL statement. The statement must start with CREATE. Commits automatically (DDL). Only available on writable connections. |
| set_trigger_statusA | Enable or disable a trigger via ALTER TRIGGER name ENABLE/DISABLE. Only available on writable connections. |
| create_procedureA | Create or replace a procedure, function, or package using a full DDL statement. The statement must start with CREATE. Commits automatically (DDL). Only available on writable connections. |
| execute_unsafe_queryA | Execute any SQL statement without restrictions. SELECT returns CSV; DML returns row count. Set auto_commit=false for a dry-run: changes are rolled back after reporting the affected row count. Only available on writable connections. |
| list_schemasA | List available Oracle connections/schemas with descriptions and readonly status. Use readonly field to determine which tools are available:
|
| sankhya_call_serviceA | Chama um serviço Sankhya via API REST. Retorna JSON da resposta incluindo status ('1'=ok, '0'=erro) e responseBody. Use sankhya_list_connections para ver as conexões disponíveis. |
| sankhya_list_connectionsA | Lista conexões Sankhya disponíveis com auth_url, base_url e status padrão. Retorna CSV com colunas: name, description, auth_url, base_url, is_default. |
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 12 tools
Most tools have clearly distinct purposes: read-only query, insert/update/delete, procedure call, DDL operations, and Sankhya service calls. The catch-all execute_unsafe_query overlaps by design but is explicitly labeled as the unrestricted fallback, so the boundaries are mostly clear.
SQL tools consistently follow a verb_noun pattern (execute_query, insert_query, create_trigger), but the Sankhya tools reverse the order with a domain prefix (sankhya_call_service, sankhya_list_connections). This mixed convention creates confusion about whether the tool name starts with the action or the domain.
12 tools is within the typical well-scoped range. The set covers both Oracle SQL operations and Sankhya service integration, though the presence of both specialized DDL tools and execute_unsafe_query introduces some redundancy.
The SQL tools cover insert, update, delete, query, procedure/trigger management, and unsafe fallback, but there is no schema discovery tool like list_tables or describe_table. The Sankhya integration is minimal (call service, list connections) and may not cover all necessary service operations.