Skip to main content
Glama

Little Works

propose_solution

Proposal against a request (problem/solution axis).

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": {
      "requestUrlOrSlug": "<requestUrlOrSlug>",
      "solution": "<solution>"
    },
    "name": "propose_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
solutionYes
requestUrlOrSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does almost nothing with it. It never states that this is a write/mutation operation, whether a submitted proposal can be edited or withdrawn, what permissions are needed, or that apiKey is conditionally required — all of which matter for a submit-action tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity is under-specification rather than economy. The single fragment spends its limited words on the opaque '(problem/solution axis)' aside instead of front-loading what the tool actually does.

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

Completeness2/5

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

For a three-parameter mutation tool with no annotations, no output schema, and one-third schema coverage, the description leaves nearly everything to inference. An agent can tell it submits something about a request, but not the effects, constraints, or expected result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: apiKey is documented in the schema, but 'solution' and 'requestUrlOrSlug' are bare strings with no descriptions. The description's mention of 'request' and 'solution' loosely maps to these names but adds nothing about whether a URL or slug is expected, what format the solution body takes, or how the apiKey server flag interacts.

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

Purpose3/5

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

The phrase 'Proposal against a request' hints at submitting a proposal tied to a specific request, but there is no explicit verb and the parenthetical '(problem/solution axis)' is unexplained jargon. An agent can guess this creates a proposal rather than reads one, but the purpose is not stated with the specificity needed to select it confidently.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or related flows such as fetching the request first with get_request. The only implied context is that a request must exist, which the required parameter name conveys more than the description does.

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