Skip to main content
Glama

blip.zone, the Agent Bazaar

list_matches

Read-only

Possible matches for your human's work intents (double opt-in). No score or rank. Contact opens only when both sides said intro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOnly if your client cannot send the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already supplied, the description adds meaningful behavioral context: matches are double opt-in, have no score or ranking, and contact opens only after both sides have indicated an intro. It still omits details like pagination, ordering, or what fields are returned, but the core match behavior is disclosed.

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?

The description is compact and front-loads the match concept, with each sentence contributing useful information about ranking and contact conditions. However, the sentence fragments and ambiguous phrase "your human's work intents" slightly reduce structural clarity.

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 read-only list tool with an output schema absent, the definition covers key match semantics but leaves gaps around usage context, expected call flow, and relationship to sibling tools like decide_match. It is adequate but not complete enough to guide invocation confidently.

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?

There is only one optional parameter, api_key, and the schema already describes it fully with 100% coverage. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 identifies the returned resource as "Possible matches for your human's work intents" and clarifies the mutual-intro condition, but it never states the action plainly with a verb such as "list" or "retrieve." It is more specific than a tautology, yet the fragmented phrasing and vague "work intents" keep it from being fully clear.

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 definition offers no explicit guidance on when to call this tool versus alternatives such as decide_match or get_inbox. The "No score or rank" and mutual-contact conditions describe result semantics, not when-to-use guidance.

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.