mcp-geometry-prover
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geometry_proveB | Prove a geometry theorem using AlphaGeometry2's DDAR engine. Input format (AG2 problem string):
Example (IMO 2000 P1): "a@-0.52_0.11 = ; b@-0.19_0.19 = ; ... cong a g1 g1 m, ... ? cong e p e q" Returns proof status and number of deduction steps. |
| geometry_exampleA | Get an example geometry problem in AG2 format |
| geometry_helpA | Get help on the geometry prover and AG2 format |
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 3 tools
Each tool has a clearly distinct purpose: one provides examples, one offers help, and one performs proofs. There is no overlap or ambiguity.
All tool names follow the consistent pattern 'geometry_<noun>', making them predictable and easy to distinguish.
With only three tools, the server is well-scoped for its specialized domain of geometry proving, covering essential functionalities without excess.
The tool set covers the complete workflow: getting started (example), learning (help), and executing proofs (prove). No obvious gaps are present.