ord-mcp-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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ord_specificationB | Get and use the latest ORD specification document |
| explain_ord_conceptA | Explain ORD concepts with examples |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ORD Specification | Latest ORD specification from GitHub |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one retrieves the specification document, the other explains concepts. There is no overlap in their purposes.
Both tool names follow a consistent verb_noun pattern: get_ord_specification and explain_ord_concept. The naming is clean and predictable.
With only 2 tools, the server feels thin for a general-purpose ORD resource, though it may be sufficient for a narrowly focused use case. It sits at the borderline end.
The server provides access to the spec and concept explanations, but lacks a way to list available concepts or navigate different versions, leaving minor gaps in discoverability.