TrustHarness
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueB | Read an untrusted issue from the synthetic repository. |
| get_pull_requestB | Read an untrusted pull request from the synthetic repository. |
| read_fileC | Read a file in the synthetic repository. |
| run_commandA | Record a simulated shell command without executing it. |
| post_commentC | Record a simulated public repository comment. |
| push_commitC | Record a simulated commit push. |
| request_approvalC | Issue approval for the canonical |
| merge_pull_requestC | Attempt a simulated pull-request merge. |
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 8 tools
Each tool targets a distinct resource or action: reading issues, PRs, files, recording commands/comments/commits, approving, and merging. The boundaries between tools are clear, with no overlapping purposes that could cause misselection.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_issue, run_command, merge_pull_request). The minor use of 'read_file' instead of 'get_file' is still in the same style and does not introduce inconsistency.
With 8 tools, the set is well-scoped for the apparent domain of simulating a repository workflow. Each tool earns its place, and the count is within the ideal range for a focused server.
The tool set covers the main PR lifecycle: reading issues/PRs, simulating commands/comments/commits, requesting approval, and merging. Minor gaps exist, such as lacking a way to list resources or modify files, but these are not critical for the core workflow.