Skip to main content
Glama

get_hint

Takes a LeetCode problem and where you're stuck, returning a targeted nudge that helps you progress without revealing the solution.

Instructions

Takes a LeetCode problem and where the user is stuck, returns a targeted nudge without revealing the solution.

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": "<problem>",
      "stuck_on": "<stuck_on>"
    },
    "name": "get_hint"
  }
}

Input Schema

NameRequiredDescriptionDefault
problemYesThe full LeetCode problem statement
stuck_onYesWhat the user is struggling with or where they are blocked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the key constraint that the response will not contain the solution and will be a 'nudge', but it says nothing about output form, length, whether hints escalate across calls, or any cost/latency behavior.

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 well-formed sentence with zero filler, and the most important constraint (no solution revealed) lands at the end of the clause where it is still prominent. Nothing is redundant or padded.

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 two-parameter tool with no output schema, the description sets the essential expectation about what the agent gets back (a non-revealing hint) and what inputs are needed. The main residual gap is that it does not characterize the returned hint's shape or how the agent should present it, which matters slightly without an output 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%, so both parameters are already documented as the problem statement and the point of blockage. The description echoes that framing ('takes a LeetCode problem and where the user is stuck') without adding format guidance such as whether the full statement text is required versus a title or URL, so the baseline of 3 applies.

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 description pairs a specific verb ('returns a targeted nudge') with a specific resource ('a LeetCode problem and where the user is stuck'), and the phrase 'without revealing the solution' implicitly separates it from solution-oriented siblings like post_solution. It stops short of naming a sibling explicitly, so the differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by 'where the user is stuck' and the no-solution constraint, which tells an agent this is for a learner who wants guidance rather than an answer. There is no explicit when-to-use versus when-to-use-a-sibling statement, and no stated prerequisites such as whether the problem statement must be complete.

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