PAARA Connector Audit
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 |
|---|---|
| score_connectorA | Score an AI connector with the PAARA seven-factor rule. Give the seven factor codes from the connector's documentation: F1 sensitive-data reach, F2 cross-system aggregation, F3 non-user-bound credentials, F4 absent logging, F5 prompt-injection exposure, F6 external sharing, F7 agentic action capability. Each code is Y (documented), N (documented absent) or U (documentation silent). Returns lower/upper score bands (Low/Moderate/High/Critical); set restricted=true if a documented write-limiting control applies, for restricted bands. |
| lookup_connectorA | Look up one of the 13 connectors in the published PAARA audit (documentation snapshot 9 Nov 2026) by name — fuzzy matching is supported, e.g. 'slack', 'Stripe MCP', 'graph'. Returns its F1-F7 codes and score bands. |
| list_connectorsA | List the 13 connectors in the published PAARA audit with their code strings and default score bands. |
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 map to distinct operations: score_connector computes a new score from supplied codes, lookup_connector retrieves a single named connector, and list_connectors returns the full set. lookup vs list overlap in that both return stored audit data, but the singular/plural split and explicit 'one of the 13' vs 'list the 13' wording makes selection clear.
All three names follow a strict verb_noun snake_case pattern (score_connector, lookup_connector, list_connectors). The verbs are conventional CRUD-style/read-style verbs applied uniformly to the same noun, so the pattern is fully predictable.
Three tools is on the thin side, but the domain is deliberately narrow: a fixed rubric applied to a 13-connector published audit. Each tool earns its place (compute, retrieve one, enumerate all), so the surface is well-scoped rather than padded.
The core lifecycle is covered: enumerate the corpus, look up an entry, and score a connector with the seven-factor rubric including restricted-band handling. Minor gaps exist — no tool to explain or validate the F1-F7 code semantics independently, and no comparison of multiple connectors — but agents can work around these by using score_connector directly.