Skip to main content
Glama

Get solution proposal details

get_solution
Read-onlyIdempotent

Get one solution proposal with its request, software, and all recorded verdicts. USE WHEN showing a proposal to the requester before confirm_solution, or checking a proposal's acceptance status. NO side effects; public. Only feedback with is_owner=true is from the original requester.

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": {
      "proposal_id": "<proposal_id>"
    },
    "name": "get_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYesProposal ID (sol_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already say readOnly=true, idempotent=true, destructive=false, and openWorld=false, so 'NO side effects; public' is largely redundant. However, 'Only feedback with is_owner=true is from the original requester' adds a genuine data-interpretation rule that no structured field carries, which is real value beyond annotations.

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?

The definition is three tight sentences, front-loading what is returned before giving usage conditions and then a data caveat. Every sentence carries information an agent needs, with no filler.

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?

There is no output schema, so the description must describe return values, and it does so by naming the included sub-objects and verdicts. Combined with the usage conditions and the is_owner caveat, an agent has enough to call this tool and interpret its output correctly.

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%, so proposal_id and its (sol_...) format are already fully documented in the schema. The description adds no further meaning about the parameter, so the baseline 3 for high-coverage schemas 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?

The description gives a specific verb and resource (get one solution proposal) and enumerates the returned composition: request, software, and all recorded verdicts. That detail distinguishes it from get_request, get_software, and get_history, which each cover only part of what this tool returns.

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?

It names two concrete triggering conditions: showing a proposal to the requester before confirm_solution, and checking acceptance status. That implies the workflow ordering (this precedes confirm_solution) without stating any explicit when-not-to-use case, so it falls just short of a 5.

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