Skip to main content
Glama

Overlap

by com.overlap-ai
OverviewDiscussionsAdmin

Confirm the draft match request

confirm_match_request

Confirm one draft match request and add it to the matching pool. The other requests of the user do not change. It stays active until the user withdraws it. Call this ONLY after the user approves the exact stored text. Always pass its request_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYesThe request_id from create_match_request or check_matches. Always name the exact request that the user approved, or asked you to withdraw.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
statusYes
request_idYes
matches_foundYes
match_limit_noteNo
pipeline_completedYesFalse when matching ran out of time. It finishes in the background.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "match_limit_note": {
+      "type": "string"
+    },
+    "matches_found": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pipeline_completed": {
+      "description": "False when matching ran out of time. It finishes in the background.",
+      "type": "boolean"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "status": {
+      "const": "open",
+      "type": "string"
+    }
+  },
+  "required": [
+    "request_id",
+    "status",
+    "matches_found",
+    "pipeline_completed",
+    "note"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description adds real side-effect scope: 'The other requests of the user do not change' and the persistence lifecycle 'stays active until the user withdraws it.' Both are behavioral facts not present in the annotations.

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?

Four short sentences, front-loaded with the action and scope, then the guardrail. Efficient, though 'Always pass its request_id' is slightly redundant with the schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation; annotations carry the safety profile; and the description supplies the missing pieces — scope of side effects, lifecycle, and the approval precondition — for a single-parameter mutation tool.

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?

Schema description coverage is 100% and the schema already explains request_id thoroughly (including its origin in create_match_request or check_matches). The description's 'Always pass its request_id' merely restates what the schema provides, so baseline 3 applies.

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?

Specific verb+resource: 'Confirm one draft match request and add it to the matching pool.' An agent can distinguish this from create_match_request and withdraw_match_request by the confirm-to-pool action. It does not explicitly name the sibling it is not, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this ONLY after the user approves the exact stored text' gives a clear precondition for invocation, and 'It stays active until the user withdraws it' implicitly points to the withdraw path. No alternative is named explicitly, so 5 is not warranted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Overlap toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources