Skip to main content
Glama

Little Works

get_anything

Get anything from Little Works: search materials, manufacturers, and labor proof. If missing, returns a request_source path — we source labor, find it, or build what does not exist.

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": {
      "query": "<query>"
    },
    "name": "get_anything"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
placeNo
queryYesWhat you need — part, trade, custom build, anything
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the fallback behavior — returning a request_source path and sourcing/building missing items — but says nothing about read-only nature, permissions, or how the search is scoped by kind or place.

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 tight sentences, with the scope front-loaded and the fallback behavior following. The opening 'Get anything' restates the name but is immediately qualified by concrete resource types.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers scope and fallback behavior reasonably but omits semantics for half the parameters and any detail about the request_source path's return shape or how sourcing works.

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 only 25%; the description adds meaning to 'query' ('part, trade, custom build, anything') and indirectly to the kind enum, but leaves 'place' and 'quantity' entirely unexplained in both schema and description.

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 names a concrete scope — searching materials, manufacturers, and labor proof — which is more specific than the tautological name 'get_anything'. It distinguishes itself as a cross-domain search tool, though it never explicitly contrasts with siblings like get_material or get_manufacturer.

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 rather than stated: it positions itself as a catch-all by describing a fallback request_source path when results are missing. However, it gives no explicit guidance on when to pick this over the narrower sibling tools such as get_material or get_manufacturer.

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