Skip to main content
Glama

dispute_idea_connection

Idempotent

Publish a visible objection. Matching source account supports account control; guest authorship claims are unverified. No automatic removal.

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": {
      "connection_id": "<connection_id>",
      "source_id": "<source_id>",
      "explanation": "<explanation>",
      "client_id": "<client_id>",
      "approved_to_publish": "<approved_to_publish>"
    },
    "name": "dispute_idea_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
modelNo
client_idYes
source_idYes
explanationYes
author_labelNo
connection_idYes
approved_to_publishYes
claim_source_authorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: the objection becomes publicly visible, source-account matching is treated as evidence of account control while guest authorship claims are not verified, and nothing is removed automatically. Those are meaningful consequences for a write with openWorldHint=true, but the phrasing is compressed to the point that an agent cannot tell exactly what state change is applied to the connection (flagged, annotated, hidden from view?).

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

Conciseness3/5

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

It is short and front-loads the action, which is good, but the middle clause ('Matching source account supports account control') is a cryptic fragment whose referent is unclear. Brevity here costs comprehension rather than saving it.

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 nine-parameter, open-world write operation with no output schema, the description omits any explanation of the parameters, the required approved_to_publish=true gate, and the resulting effect on the disputed connection. It covers visibility and non-removal but leaves too much of the call contract unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across nine parameters, so the description carries the full explanatory burden and largely does not: connection_id, source_id, explanation, client_id, and approved_to_publish are never mentioned. Only 'matching source account' faintly gestures at source_id/claim_source_author, without defining either.

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?

The first sentence gives a concrete verb and outcome: publishing a visible objection (a dispute) against an idea connection. The target resource is only inferable from the tool name, and no sibling (e.g. create_idea_connection) is named, but the action itself is unambiguous.

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 statement of when to dispute a connection versus when to use create_idea_connection or another sibling, and no prerequisites or preconditions for calling it. The remaining clauses describe provenance and moderation behavior, not usage selection.

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