Skip to main content
Glama

Little Works

match_suppliers

Supplier graph: who can fulfill a need so we can invite them into the bid cycle.

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": "match_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes
placeNo
supplierNoHint from procurement log

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description bears the full burden and delivers almost nothing: it does not say whether this is a read-only lookup, how results are ranked or scored, whether it hits a network/graph service, or what happens when no supplier matches. The word 'graph' hints at relational traversal but is never elaborated.

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?

One short sentence with the resource front-loaded and zero padding. It is terse rather than bloated, so brevity is not the problem — the issue is that so little content is packed into the brevity.

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 three-parameter matching tool with no annotations and no output schema needs the description to explain both invocation semantics and what comes back. The description supplies neither, leaving the agent unable to predict result shape, ranking, or empty-match behavior.

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% — the single documented parameter is 'supplier' ('Hint from procurement log') — and the description adds no meaning for the required 'need' or the optional 'place'. It does not explain how place constrains matches or how the supplier hint biases results, so the gaps in the schema are left unfilled.

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 fragment 'Supplier graph: who can fulfill a need' names the resource (suppliers) and the intent (fulfilling a need), but offers no explicit verb such as 'find' or 'match'. An agent can infer a matching/lookup operation, but the phrasing is elliptical and gives no differentiation from siblings like match_proof or discover_capabilities.

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 only usage hint is the downstream motive 'so we can invite them into the bid cycle', which implies pre-bid sourcing but states no when-to-use condition, no prerequisites, and no alternative tool to prefer in other situations. Nothing tells the agent when NOT to call this.

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