okf-ons
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| okf.descriptor | Return the pinned metadata-only corpus descriptor, scope boundaries, entrypoints, outcome codes and material caveats. Makes no network request. |
| okf.search | Rank compact candidates from a non-empty intent or identifier query and show nearby alternatives before selection. |
| okf.get_recordA | Resolve an exact stable ID, native ID, route or declared evaluation alias and return the complete frozen metadata record. |
| okf.compareA | Return evidence-backed field contrasts for two to five exact records. Never asserts statistical equivalence. |
| okf.prepare_mcp_planB | Bind the exact frozen identity and snapshot digest to its inspection/query tools, audience, purpose and caller-declared expiry. Preserve unresolved dimensions and reject credential fields. Never authorises or executes a query. |
| okf_eval.submit_answerA | Validate and return a deterministic, non-persisted evaluation envelope. Accepts visible answers, evidence and caveats, never hidden reasoning. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OKF-ONS descriptor | Pinned scope, orientation and caveat contract. |
| OKF-ONS agent profile | Read-only access and selection workflow. |
| OKF-ONS selection contract | Rules for a non-executing MCP hand-off. |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: record retrieval, comparison, plan preparation, and answer submission. No functional overlap exists.
Names mix dot notation (okf.get_record) and underscore (okf_eval.submit_answer), with inconsistent prefixes (okf vs okf_eval) and verb forms (compare vs prepare_mcp_plan).
4 tools is on the lower side but may be appropriate for a narrow domain. However, the descriptions suggest a more complex system that could benefit from additional tools.
Missing fundamental operations such as creating, updating, listing, or searching records. The tool set feels incomplete for the implied workflow.