Skip to main content
Glama

Little Works

name_problem

Create / draft a work-order style request (problem, place, willing-to-pay).

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>"
    },
    "name": "name_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
problemYes
willingToPayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden, yet it says nothing about whether the request is persisted, what status it starts in, whether 'willing to pay' implies a commitment, or what auth is required (only the schema hints at apiKey). The draft-versus-create ambiguity is left unresolved, which matters for a mutation tool.

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?

A single compact sentence with the affected fields front-loaded in parentheses; nothing is padded. The slash construction 'Create / draft' saves space but introduces ambiguity rather than clarity.

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 mutation tool with no annotations, no output schema and 75% of parameters undocumented in the schema, the description is far too thin. An agent cannot tell what happens on success, what apiKey gating means for calling it, or how the resulting request relates to get_request.

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 25% (only apiKey is documented in the schema), so the description should compensate. It merely repeats the parameter names 'problem, place, willing-to-pay' without explaining formats — no guidance on whether place is a city, address or ID, or what units willingToPay accepts beyond the schema's string|number type.

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 description does name a resource ('work-order style request') and the fields involved, but the verb is hedged as 'Create / draft', leaving unclear whether a persistent request is created or just a draft prepared. Nothing distinguishes it from the many other creation-style siblings such as create_booking, and the tool name 'name_problem' is too opaque to compensate.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of a related tool like get_request to confirm a request is created and then retrievable. The agent must infer usage entirely from the parenthetical field list.

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