company-reconcile
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to listen on. | 8000 |
| MCP_API_KEY | No | Optional API key for authentication. If set, requests must include header X-Api-Key: <key>. | |
| MCP_HTTP_PATH | No | The HTTP path for the MCP service endpoint. | /mcp |
| MCP_TRANSPORT | No | The transport type: 'streamable-http' or 'stdio'. | streamable-http |
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 |
|---|---|
| reconcile_company_tablesA | 把两份表格按【公司名称 + 日期】做模糊对碰 (AND逻辑: 名称与日期都满足才算匹配)。 返回三档结果:
|
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 1 tool
With only one tool, there is no risk of confusion between tools. The tool's purpose is clearly defined.
The single tool uses a descriptive snake_case verb_noun pattern. Consistency is not an issue with only one tool.
A single tool for company reconciliation is borderline; it bundles multiple operations (matching, reviewing, summarizing) into one, which may lack modularity.
The tool covers the core reconciliation process, but lacks separate controls for thresholds, detailed inspection of unmatched items, or history features.