Skip to main content
Glama
PAARA Connector Audit

PAARA Connector Audit

list_connectors

Lists all 13 connectors in the published PAARA audit, including code strings and default score bands, so you can identify available connectors for governance scoring.

Instructions

List the 13 connectors in the published PAARA audit with their code strings and default score bands.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the return payload shape (code strings plus default score bands) and the fixed cardinality of 13, which is genuinely useful, but it says nothing about whether the result is a static snapshot of a published audit or can change, nor whether 'default score bands' are editable via score_connector.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler, and the key identifiers (13 connectors, PAARA audit) are front-loaded before the return details. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with no output schema, the description covers what an agent most needs: scope (the published PAARA audit) and the fields returned. A sentence tying the returned code strings to lookup_connector or score_connector would close the remaining workflow gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It appropriately spends its words on the return content instead of inventing input detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb (List) against a concrete resource (the 13 connectors in the published PAARA audit) and even names what each entry carries (code strings, default score bands). It stops short of explicitly differentiating itself from lookup_connector or score_connector, so an agent must infer that this is the bulk-enumeration variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: because it returns all 13 connectors with their code strings, an agent can deduce this is the entry point for discovering codes before calling lookup_connector or score_connector. There is no explicit 'use this when...' statement, no exclusion of alternatives, and no note on whether codes from here are required inputs elsewhere.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools