Skip to main content
Glama

get_problem

Read-onlyIdempotent

Retrieve in-depth community consensus details, all verified workarounds, direct quotes, and venue distribution for a specific software dilemma by slug or URL.

Usage Guidelines:

  • Deep inspection tool: use AFTER discovering a dilemma slug via 'search_problems' (or when given an exact SaidItHere slug / problem URL).

  • Sibling routing: do NOT use for open keyword discovery or exploratory queries; call sibling tool 'search_problems' instead.

  • If a slug is invalid or not found, fall back to 'search_problems' with broader search terms.

Behavior & Side Effects:

  • Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.

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": {
      "slug": "<slug>"
    },
    "name": "get_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe exact dilemma slug (e.g. 'coping-with-unexpected-software-subscription-price-increases') or full SaidItHere URL (e.g. 'https://saidithere.com/problems/...').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The dilemma slug (e.g. 'coping-with-unexpected-software-subscription-price-increases') or full SaidItHere URL"New value: +"The exact dilemma slug (e.g. 'coping-with-unexpected-software-subscription-price-increases') or full SaidItHere URL (e.g. 'https://saidithere.com/problems/...')."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, and the 'Behavior & Side Effects' section largely restates them ('pure read-only, safe, and idempotent'), earning no extra credit. The genuinely additive behavioral content is the invalid-slug fallback and the enumeration of returned content, which is useful but thin given annotations already carry the safety profile.

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 purpose, then cleanly sectioned into usage and behavior, and the routing warning appears early. It loses a point for the 'Behavior & Side Effects' block, which spends three sentences repeating what the annotations already encode rather than adding new information.

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

Completeness5/5

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

For a one-parameter read tool with a fully documented schema, the description covers selection, sequencing, failure handling, and the shape of the returned content even though no output schema exists. Nothing an agent needs in order to call it correctly 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 the single 'slug' parameter is documented with slug and full-URL examples in the schema itself. The description's 'by slug or URL' adds nothing beyond that, so the baseline of 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 ('Retrieve') and a concrete resource set — community consensus, verified workarounds, direct quotes, venue distribution — scoped to 'a specific software dilemma by slug or URL'. This is clearly distinguishable from the keyword-discovery sibling, so an agent can pick it without opening the 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 positions the tool as a deep-inspection step that must follow 'search_problems', names the exact anti-pattern ('do NOT use for open keyword discovery'), and prescribes a recovery path when the slug is invalid. Both the when and the when-not are stated with the alternative named.

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