Skip to main content
Glama

Little Works

request_source

Actually source materials / anything: creates a real Discover job + one bid cycle per line (supplier graph matched). Service is any transaction.

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": {
      "need": "<need>"
    },
    "name": "request_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
needYesWhat to source or build
linesNoProcurement lines — each becomes its own bid cycle
notesNo
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
quantityNo
projectTitleNo
willingToPayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lines
      Added value: +{
      +  "description": "Procurement lines — each becomes its own bid cycle",
      +  "items": {
      +    "properties": {
      +      "csi": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "quantity": {
      +        "type": "number"
      +      },
      +      "sku": {
      +        "type": "string"
      +      },
      +      "spec": {
      +        "type": "string"
      +      },
      +      "supplier": {
      +        "type": "string"
      +      },
      +      "unit": {
      +        "type": "string"
      +      },
      +      "unitPrice": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / projectTitle
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

C2.6/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, and it does disclose the key side effect: a real Discover job is created and each line spawns its own bid cycle with supplier graph matching. It omits irreversibility, cost/commitment implications, and what happens on partial failure, and the API key requirement is left to the schema.

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

Conciseness3/5

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

It is short and the core action is front-loaded, but the trailing fragment "Service is any transaction" is unparseable and does not earn its place. One wasted clause in an already minimal description is a meaningful proportion of the content.

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?

A 9-parameter, side-effecting tool with no output schema and low schema coverage needs far more: what a Discover job is, what the agent gets back, and what the non-obvious parameters mean. The description explains only the line-to-bid-cycle mechanic and leaves the rest of the call surface unexplained.

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 coverage is only 33% across 9 parameters, so the description needs to compensate and largely does not. It clarifies the "lines" concept (one bid cycle per line) but says nothing about the kind enum, place, willingToPay, quantity, notes, projectTitle, or apiKey, and the opaque "Service is any transaction" hint adds no actionable meaning.

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?

"Creates a real Discover job + one bid cycle per line" is a concrete action statement, but the leading clause "Actually source materials / anything" is vague and the closing fragment "Service is any transaction" muddies rather than clarifies. It does not distinguish itself from close siblings such as source_materials_for_job or source_people, so an agent must still infer which sourcing tool to pick.

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?

The word "Actually" weakly implies this is the real (non-preview) path versus something else, but no alternative tool is named and no condition for choosing it is given. There is no guidance on when not to use it, what prerequisites apply, or how it relates to buy_material / source_materials_for_job.

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