Skip to main content
Glama

suggest_dilemma

Submit a new software friction, unresolved developer dilemma, or tool gotcha to SaidItHere's automated crawler pipeline for cross-platform consensus investigation.

Usage Guidelines:

  • Ingestion request tool: use ONLY when sibling tool 'search_problems' returns zero matching dilemmas, or when the user explicitly requests to submit an unindexed developer pain point to the platform.

  • Sibling routing: do NOT use if 'search_problems' already returned relevant dilemmas with established community workarounds.

Behavior & Side Effects:

  • State-modifying write operation (non-idempotent). Queues a new topic suggestion in the ingestion backlog for automated moderation and cross-platform spidering. Does not delete or overwrite existing data.

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": {
      "problem_description": "<problem_description>"
    },
    "name": "suggest_dilemma"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional additional context regarding why this issue is painful, breaking changes, or user impact.
platforms_or_linksNoOptional URLs or community platform names where developers are actively discussing this issue (e.g. 'Reddit r/sysadmin', 'https://github.com/nodejs/node/issues/1234').
problem_descriptionYesClear, concise description of the software friction, bug gotcha, or tooling dilemma to investigate (e.g. 'Node gyp build failure on Windows 11 ARM64'). Minimum 5 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional additional notes on why this is painful"New value: +"Optional additional context regarding why this issue is painful, breaking changes, or user impact."
    • changedInput schema / properties / platforms_or_links / description
      Previous value: -"Optional link or platforms where developers are discussing this (e.g. 'Reddit r/sysadmin')"New value: +"Optional URLs or community platform names where developers are actively discussing this issue (e.g. 'Reddit r/sysadmin', 'https://github.com/nodejs/node/issues/1234')."
    • changedInput schema / properties / problem_description / description
      Previous value: -"Clear, concise description of the software friction or dilemma"New value: +"Clear, concise description of the software friction, bug gotcha, or tooling dilemma to investigate (e.g. 'Node gyp build failure on Windows 11 ARM64'). Minimum 5 characters."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the downstream effect: the topic enters an ingestion backlog, undergoes automated moderation, and is spidered across platforms. It also confirms no existing data is deleted or overwritten, which reinforces destructiveHint=false, though 'non-idempotent' largely restates idempotentHint=false. It does not describe what the caller receives back, but the behavioral picture is otherwise clear.

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?

Front-loaded with the core action in the first sentence, then organized into labeled sections for routing and side effects. Slightly verbose for a three-parameter tool, but every section carries usable information rather than filler.

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

Completeness4/5

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

For a simple non-destructive write with full parameter documentation and no output schema, the description covers purpose, routing, and side effects adequately. The one gap is that it doesn't indicate what confirmation or identifier the caller gets back, which would matter for a queuing operation.

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%, so all three parameters are already documented with examples and constraints (minimum 5 characters). The description adds no additional parameter guidance, which is appropriate given the schema does the work; baseline 3 applies.

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

Purpose5/5

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

States a specific verb ('Submit a new software friction, unresolved developer dilemma, or tool gotcha') and an explicit destination ('SaidItHere's automated crawler pipeline'). An agent can distinguish this ingestion tool from read-only siblings like search_problems and get_problem without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the condition for use (search_problems returns zero matches, or the user explicitly asks to submit an unindexed pain point) and the exclusion (do not use when relevant dilemmas with workarounds already exist). Sibling routing is spelled out rather than inferred.

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