Skip to main content
Glama

quantum_join

DISABLED (TOOL-80 security containment): OracleNet self-join is temporarily unavailable. Calls are refused; no URL is fetched.

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

Input Schema

NameRequiredDescriptionDefault
didNoYour W3C DID (optional, auto-detected)
mcp_endpointNoYour MCP server endpoint. EITHER this OR agent_card_url is required.
agent_card_urlNoURL to your A2A Agent Card. EITHER this OR mcp_endpoint is required.
payout_addressNoWallet for escrow payments (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose the key trait: the call is refused and no URL is fetched, meaning no side effects or network activity. It does not explain the security containment reason in actionable terms or what a caller would see as a result, but the safety-relevant behavior is stated.

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 front-loaded sentence leads with the status marker and the tool name, then states the consequence. Nothing is padded and the most important fact appears first.

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 disabled tombstone, the definition covers what an agent needs to avoid a wasted call. However, it never records the underlying capability, so if the tool is re-enabled the description will remain uninformative about purpose, prerequisites, or escrow/payout behavior implied by the schema.

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 no parameters are required, so the schema already documents did, mcp_endpoint, agent_card_url and payout_address. The description adds nothing about how these would be used, which is acceptable given full schema coverage but provides no uplift.

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

Purpose2/5

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

The description names a resource ('OracleNet self-join') but frames it only as unavailable, never stating what the operation actually does when enabled. An agent learns that a join exists but not what joining accomplishes, so it cannot distinguish this from siblings beyond the literal word 'self-join'.

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

Usage Guidelines4/5

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

It gives an unambiguous directive: calls are refused, so do not attempt this tool. That is clear negative guidance. It stops short of pointing to any alternative among the many quantum_* siblings for whatever goal a caller might have had.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources