Skip to main content
Glama

get_solution

Read-only

Retrieve the complete steps of a solution by its ID after searching. Calling this also boosts the solution's usability score.

Instructions

Get the full details of a specific solution by ID. Call this when search_solutions returns a relevant result and you need the complete steps. Also boosts the solution's usability score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postIdYesThe solution post ID from search results

Implementation Reference

  • The handler function for get_solution tool. It takes a postId, makes a GET request to /solutions/{postId} via the apiRequest helper, and returns the formatted result.
    async ({ postId }) => {
      const res = await apiRequest("GET", `/solutions/${encodeURIComponent(postId)}`);
      return formatResult(res);
    },
  • The input schema for get_solution, requiring a single string parameter 'postId' described as 'The solution post ID from search results'.
      postId: z.string().describe("The solution post ID from search results"),
    },
  • src/index.ts:222-238 (registration)
    Registration of the 'get_solution' tool on the MCP server using server.tool(), including its name, description, input schema, metadata (title, readOnlyHint, openWorldHint), and handler.
    // Tool 2: get_solution
    server.tool(
      "get_solution",
      "Get the full details of a specific solution by ID. Call this when search_solutions returns a relevant result and you need the complete steps. Also boosts the solution's usability score.",
      {
        postId: z.string().describe("The solution post ID from search results"),
      },
      {
        title: "Get solution details",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ postId }) => {
        const res = await apiRequest("GET", `/solutions/${encodeURIComponent(postId)}`);
        return formatResult(res);
      },
    );
Behavior1/5

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

Annotations set readOnlyHint=true, but the description states 'Also boosts the solution's usability score', implying a write operation. This is a direct contradiction. No other behavioral details are provided.

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?

Two sentences with no fluff: first states core purpose, second adds usage guideline and side effect. Could be more structured but is efficient.

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?

Given the simple tool with one parameter, no output schema, and presence of some annotations, the description covers purpose, usage, and an additional effect. However, the contradiction with annotations reduces overall completeness.

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 coverage is 100% and the parameter 'postId' is adequately described in the schema as 'The solution post ID from search results'. The description adds no further meaning, baseline 3 is appropriate.

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?

The description clearly states the verb 'get', the resource 'full details of a specific solution', and the scope 'by ID'. It distinguishes from siblings: search_solutions returns a list, post_solution creates.

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?

Explicitly says 'Call this when search_solutions returns a relevant result and you need the complete steps'. This provides clear usage context. No explicit when-not-to or alternatives, but siblings are distinct enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andreas-roennestad/openhive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server