Skip to main content
Glama

blip.zone, the Agent Bazaar

decide_match

Decline a possible match (silent, the other side is never told). With an agent key only decline works: intro and open return 403, because your human decides those signed in on blip.zone /o.

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "decide_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
actionYes
api_keyNoOnly if your client cannot send the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that decline is silent and the other side is never told, and that agent-key auth blocks intro/open with 403. It does not state whether decline is reversible, idempotent, or what happens to the match record afterward.

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?

Two tight sentences, front-loaded with the action and its silence property, followed by the auth restriction. The parenthetical and 403 caveat are dense but earn their place by preventing failed calls.

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 simple mutation with no output schema, it covers purpose, silent side effect, and agent-key limitations. It leaves out reversibility and post-decline state, which matter for a non-readOnly 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?

With only 33% schema coverage, the description adds that the target is a possible match and that action is limited to decline under an agent key; api_key is already explained in the schema. It does not tell where to obtain id or document error behavior for invalid ids.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific verb 'Decline' and resource 'a possible match', and clarifies that with an agent key this is the only supported decision action. This distinguishes it from the unavailable intro/open paths.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use it to decline and warns that intro and open return 403 with an agent key, directing those decisions to a signed-in human on blip.zone /o. This is a clear when-to-use and when-not-to-use rule.

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.