Skip to main content
Glama

Belline Connect

Accept the suggested time

accept_proposal
Idempotent

Accepts the other time the business suggested. It works only while the inquiry's status is 'proposed'. The suggested time becomes the message and the status becomes accepted.

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>"
    },
    "name": "accept_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id create_inquiry returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world mutation, so the description's job is to say what actually changes — and it does: the suggested time is written into the message and the status flips to 'accepted'. What is not disclosed is the failure behavior when the status is not 'proposed' (error vs. silent no-op) or whether prior message content is overwritten.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose first, precondition second, resulting state changes last. Every sentence carries information and none repeats the title or the schema.

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

Completeness4/5

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

For a one-parameter state-transition tool this covers the essentials: the action, the gating status, and the two resulting mutations. The only gap is the return value, which is undocumented since no output schema exists, so the agent cannot anticipate the response shape.

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 coverage is 100% and the sole parameter 'id' already documents that it comes from create_inquiry, so the schema carries the load. The description adds no further meaning about the id, which is acceptable but nothing above baseline.

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?

"Accepts the other time the business suggested" gives a specific verb and a precise resource (the business-suggested time), which separates it from book_slot (choosing your own slot) and ask_business. It stops short of explicitly naming the sibling it competes with, so discrimination is inferred rather than stated.

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?

"It works only while the inquiry's status is 'proposed'" is a concrete precondition that tells the agent when this call is valid, which is more than most definitions offer. It does not name an alternative to use when the status is not 'proposed', leaving the fallback path (e.g. book_slot or ask_business) to inference.

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