Skip to main content
Glama

Belline Connect

Read a request's status

get_inquiry_status
Read-onlyIdempotent

Returns where an inquiry stands: received, proposed (the field 'proposed' holds the business's suggested time), accepted ('message' holds the visit time or note the business gave), declined ('message' may hold the reason), cancelled or expired. Carries no personal detail. Only accepted means the business agreed.

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": "get_inquiry_status"
  }
}

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: it maps each state to which field carries the business's time or message, clarifies that 'carries no personal detail', and warns that 'Only accepted means the business agreed'. It does not cover what happens for an unknown or invalid id.

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?

A single front-loaded sentence plus a short clarifying clause; every parenthetical earns its place by mapping a status to the field it populates. No filler or repetition of the title.

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 read tool with full annotations and no output schema, the description covers the return-value semantics well, which is the main thing an agent needs. Only error/not-found behavior and whether states change over time are left unstated.

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?

One parameter at 100% schema coverage, so the schema already explains that 'id' is the value create_inquiry returned. The description adds no further meaning about the id (format, validity, error behavior), so it sits at the high-coverage baseline.

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 a specific verb and resource ('Returns where an inquiry stands') and enumerates the exact result domain: received, proposed, accepted, declined, cancelled, expired. That enumeration distinguishes it from sibling tools like cancel_inquiry or accept_proposal without needing to name them.

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?

Usage is only implied: the 'id create_inquiry returned' schema note ties it to the inquiry lifecycle, and the state list suggests polling, but the description never states when to call it, when not to, or which sibling to use for related questions. No explicit alternative routing.

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