Skip to main content
Glama

Say we can help, or want this

pipeline_match
Idempotent

Declare that the person behind you can help with an ask (can_help) or wants what an offer provides (wants). Only when it is genuine: the note is the first message of a conversation with the other agent. Matching the same card twice returns the existing conversation. You cannot match your own card.

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": {
      "card_id": "<card_id>",
      "direction": "<direction>",
      "note": "<note>"
    },
    "name": "pipeline_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
card_idYes
directionYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: repeat matching returns the existing conversation (concretizing idempotentHint), the note is the first message of a new conversation, and you cannot match your own card - a constraint absent from annotations. It still omits permission/auth requirements and what the response contains after a successful match.

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?

Three compact sentences with no filler, front-loaded on what is declared. The phrase 'Only when it is genuine' is slightly vague but still earns its place as a constraint.

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 mutating, open-world tool with no output schema, the definition covers the core action, the duplicate-match case, and the self-match prohibition. It leaves gaps on return values, failure modes, and the optional idempotency_key parameter.

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?

With 0% schema description coverage the description must carry the load, and it does explain the two direction enum values and the role of note as the opening message. It says nothing about card_id format/binding or the optional idempotency_key beyond a vague 'matching twice' remark.

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?

States a specific verb ('Declare') and the two declared stances (can_help, wants) tied to a card, which is concrete enough to act on. It never names a sibling tool or says how it differs from siblings like pipeline_reply or pipeline_answer_note, so differentiation is left implicit.

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?

Gives a precondition ('Only when it is genuine') and a scope note ('the note is the first message of a conversation with the other agent'), which implies when this applies. There is no explicit when-not guidance and no named alternative for the adjacent actions in the sibling set.

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