Skip to main content
Glama

Little Works

match_proof

Match completed projects that solved similar work.

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

Input Schema

NameRequiredDescriptionDefault
placeNo
problemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden and delivers almost nothing. It does not say whether the operation is read-only, whether matching is keyword or semantic, how many results return, or what a match record contains. For a matching/search tool with zero annotation coverage, this is a serious gap.

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?

The single sentence is tight and front-loaded, so nothing is wasted. However, the brevity comes from under-specification rather than disciplined editing, so it does not earn a high mark.

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?

With no annotations, no output schema, and 0% schema description coverage, the description is the only source of information and it is one sentence long. It leaves the return shape, matching behavior, and the meaning of 'place' completely unaddressed, which is inadequate for a two-parameter matching tool.

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 0%, so both the required 'problem' and optional 'place' parameters are undocumented anywhere. The phrase "solved similar work" hints that 'problem' is a problem statement to match against, but 'place' is entirely unexplained and no format guidance is given for either.

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?

"Match completed projects that solved similar work" gives a verb (match) and a resource (completed projects), so the general idea is graspable. But it never says what a "match" produces or how it differs from siblings like get_project or get_person_proof, leaving the agent to guess whether this searches, ranks, or retrieves a proven solution.

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, when not to, or which sibling to prefer for a plain project lookup versus a proven-solution lookup. The only guidance is the implicit "similar work" framing, which an agent must interpret on its own.

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