Skip to main content
Glama
Sign In

syntropy-mcp

by io.github.macek166
OverviewDiscussionsAdmin

syntropy_list_connectors

List all registered Custom Epistemic Connectors attached to a Small World (with secret headers redacted).

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": {
      "world_id_or_handle": "<world_id_or_handle>"
    },
    "name": "syntropy_list_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault
world_id_or_handleYesSmall World handle or UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 behavioral burden. It does disclose one genuinely useful trait not available elsewhere: secret headers are redacted in the output. It omits permission requirements, pagination/result limits, and what happens with an unknown or inaccessible handle.

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 front-loaded sentence with the core action first and the redaction caveat correctly demoted to a parenthetical. No filler, though the parenthetical could have been folded in more plainly.

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 single-parameter read tool this is close to sufficient, and the redaction note is valuable. With no output schema, however, the description never indicates what a returned connector record contains (id, name, endpoint, status), leaving the agent to discover the response shape by calling it.

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?

The single parameter is fully documented in the schema ("Small World handle or UUID"), covering 100% of inputs. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb ("List") and a precisely scoped resource ("registered Custom Epistemic Connectors attached to a Small World"), so the agent knows exactly what it retrieves. It does not name or distinguish itself from siblings like syntropy_query_connector or syntropy_register_connector, which keeps it 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?

There is no explicit guidance on when to choose this over syntropy_query_connector, syntropy_register_connector, or the world/axiom tools. Usage is only inferable from the word "List"; no prerequisites, exclusions, or alternative routing are given.

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

All syntropy-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources