Skip to main content
Glama

discover_protocols

Discovers peer MCP instances and their shared protocols, enabling cross-instance protocol sharing so swarms can synchronize behavior across parallel workers.

Instructions

Discover peer MCP instances and their protocols. Enables cross-instance protocol sharing.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "discover_protocols"
  }
}

Input Schema

NameRequiredDescriptionDefault
startSyncNoStart synchronization service (default: false)
projectDirYesAbsolute path to the project directory
refreshPeersNoRefresh the list of known peers (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and does not disclose that the optional startSync flag appears to launch a synchronization service or that refreshPeers defaults to true, both of which imply side effects not evident from reading the name. Nothing is said about network access, permissions, or whether discovery is a pure read, which for a peer-discovery tool is a meaningful gap.

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?

Two short sentences, zero filler, and the core action is front-loaded before the motivation clause. The second sentence is mildly redundant with the first but does add the sharing purpose.

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

Completeness2/5

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

For a three-parameter tool with no annotations and no output schema, the description leaves the agent unsure whether this is a read-only discovery call or one that starts a background sync service, and it does not indicate what the returned discovery data looks like. The schema covers syntax, but the behavioral picture an agent needs to call it safely is missing.

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

Parameters3/5

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

Schema description coverage is 100% and all three parameters (projectDir, startSync, refreshPeers) already carry descriptions and defaults, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which is the baseline case for full schema coverage.

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?

"Discover peer MCP instances and their protocols" gives a specific verb and resource with a clear scope (peer discovery), which distinguishes it from the protocol transfer siblings like import_protocols or sync_protocols. It stops short of explicitly naming or contrasting those siblings, so it falls short of a 5.

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?

The description offers no when-to-use guidance, no prerequisites, and no mention of when a caller should prefer export/import/sync_protocols instead. The phrase "Enables cross-instance protocol sharing" gestures at a context but never states a condition for selecting this tool.

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