freshprobe
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| freshprobe_batchB | Probe multiple endpoints concurrently for data freshness. Returns an array of JSON verdicts. |
| freshprobe_checkA | Probe a single endpoint for data freshness and liveness. Returns a deterministic JSON verdict with freshness score, latency percentiles, TLS status, and content fingerprint. |
| freshprobe_policyA | Check an endpoint against a named freshness policy. Returns verdict with pass/fail evaluation against policy thresholds. |
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
The three tools are mostly distinct: batch probes multiple endpoints, single checks one endpoint in detail, and policy evaluates against thresholds. The slight overlap between batch and single could cause minor confusion, but descriptions clarify the differences well.
All tools follow a consistent 'freshprobe_' prefix with clear action verbs (batch, check, policy). The naming pattern is predictable and readable, though the prefix is not a standard verb_noun pattern.
With 3 tools, the server is compact and covers the core functionality of probing freshness: single check, batch check, and policy evaluation. The count feels slightly thin but is appropriate for a focused utility server.
The tool surface covers probing, batch probing, and policy evaluation, but lacks management operations like creating/updating policies or listing endpoints. Key workflows are present, but there are notable gaps for a policy-based system.