Skip to main content
Glama
PAARA Connector Audit

PAARA Connector Audit

lookup_connector

Find a connector in the PAARA audit by name or fuzzy match, then retrieve its F1–F7 codes and score bands for governance review.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful traits: the data is a fixed published snapshot dated 9 Nov 2026, the universe is only 13 connectors, matching is fuzzy/approximate, and the response shape is described. It omits error or no-match behavior and does not state read-only nature explicitly, which is a minor gap for a lookup tool.

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 dense sentence that front-loads the action, then scope, then semantics, then return value, with no filler. Every clause carries information an agent needs.

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 one-parameter lookup with no output schema, the definition covers scope, matching behavior, snapshot provenance, and returned fields, which is close to complete. The only real gap is what happens on an unmatched name, which matters for a fuzzy-match tool.

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?

Schema coverage is 0% with one required parameter, so the description must compensate, and it does: it explains the parameter is a connector name, that matching is fuzzy, and gives three concrete example inputs spanning a lowercase slug, a title-cased multiword name, and a substring. Format constraints beyond that (case sensitivity details, partial-token rules) are not specified.

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 and resource: looks up a connector from the PAARA audit by name, and bounds the corpus at 13 connectors with a dated snapshot. It also states the return payload (F1-F7 codes and score bands). It does not explicitly distinguish itself from siblings like list_connectors or score_connector, though 'by name' implies the difference.

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: the reader infers this is for fetching details about a known connector, and fuzzy matching ('slack', 'Stripe MCP', 'graph') clarifies input expectations. There is no explicit when-to-use versus list_connectors or score_connector, and no guidance on what to do when nothing matches.

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