Skip to main content
Glama

probe_peers

Detects installed peer transports—CLIs on PATH, API keys in environment, MCP servers in mcp.json, and Slack CLI fingerprint—so agents can route work to the correct integration.

Instructions

Detect which peer transports are installed: CLIs on PATH, API keys in env, MCP servers in mcp.json, Slack CLI fingerprint.

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": "probe_peers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the exact inspection sources (PATH, environment variables, mcp.json, Slack fingerprint), which implies a read-only local probe, but it doesn't state whether it returns key values or only presence, whether it shells out to CLIs (cost/latency), or whether any network call occurs.

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

Conciseness4/5

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

One dense sentence with the outcome ('detect which peer transports are installed') front-loaded and the detection sources listed after the colon. No filler, though the colon list consumes the entire space that could have held a return-shape note.

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

Completeness3/5

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

For a zero-param, side-effect-free probe with no output schema, the critical missing piece is what the result looks like — a map of transport to availability, a list of strings, or a flat status? That absence, plus no note on whether env/CLI presence is reported safely, leaves a real gap for such a simple 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the description contradicts the empty schema.

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?

Specific verb 'detect' plus a concrete resource ('peer transports'), with an explicit enumeration of what is inspected: CLIs on PATH, env API keys, MCP servers in mcp.json, Slack CLI fingerprint. It doesn't contrast itself with siblings like list_peers, but an agent can still tell this is an environment-probing tool rather than a listing/calling tool.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no mention of alternatives such as list_peers for enumerating peers versus probing for installed transports. The purpose sentence implies a discovery-before-invocation role, but the agent is left to infer that sequencing entirely.

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