Skip to main content
Glama

Loomivo: verified local businesses

get_request_status

Whether the business confirmed a request (by its ref), with a price for quotes.

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": {
      "ref": "<ref>"
    },
    "name": "get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key behavioral fact that the response includes a quote price only in the quote case, which is useful. It does not state what happens for an unknown ref (error vs. not-found status), whether a request can exist before business confirmation, or any auth requirement, leaving meaningful gaps for a status-lookup tool.

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?

One short sentence with no filler, and the core concept (confirmation status) is front-loaded. The fragmentary phrasing ('Whether the business confirmed...') is slightly awkward but costs no clarity.

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 one-parameter read tool with no output schema and no annotations, the description covers the essential return content but not edge behavior (invalid ref, unconfirmed vs. non-existent request) or the shape of the price field. Adequate to attempt a call, but an agent would still be guessing at failure modes.

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 0%, so the description must compensate for the single undocumented parameter; 'by its ref' does identify ref as the request reference identifier, which is real added meaning. However, it says nothing about ref format, case sensitivity, or where the ref originates, so compensation is only partial.

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?

The description names the resource (a request, identified by its ref) and the information returned (business confirmation plus a price for quotes), which is specific enough to separate it from create_request or get_business. It is phrased as a result statement rather than a verb-led action, which slightly muddies whether it fetches or evaluates, but the intent is still clear.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus siblings such as create_request or get_available_times, and no stated preconditions (e.g., the ref must come from create_request). The '(by its ref)' aside implies the lookup key but not the usage context.

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