Skip to main content
Glama

Bookvia

Get business profile

get_business_profile
Read-onlyIdempotent

Full verified profile of one business: services with price ranges, service area, opening hours, request policy and the information the business needs to answer a request. An ID from the unverified list (lst_…) has no profile: the answer then is the error unverified_listing with the public basic data.

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": {
      "business_id": "<business_id>"
    },
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYesID from search_businesses

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
remoteNotrue: the business also works online or by phone for customers anywhere in Germany
addressYes
contactYes
industryYes
servicesYes
categoriesYes
booking_urlNoPage where the customer can book an appointment directly with the business. Give it to the customer; booking there does not go through Bookvia
descriptionYes
reachabilityNoHow fast the business usually reacts during and outside opening hours, as stated by the business. Tell the customer, never promise. The binding deadline is request_policy.response_time_hours. null: the business has not said yet.
service_areaYes
verificationYes
opening_hoursYes
request_policyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-open-world and idempotent, so safety is covered. The description adds real behavioral context beyond that: what the response contains and, importantly, the exact failure mode for lst_ prefixed IDs (error unverified_listing plus public basic data). It does not cover behavior for a nonexistent or malformed ID.

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 dense sentences, front-loaded with the payload summary before the edge case. The phrase 'the information the business needs to answer a request' is slightly vague, but nothing is wasted.

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?

Output schema exists, so return shape need not be re-described; annotations carry the safety profile; the single parameter is fully documented. The description closes the remaining gaps (payload contents, unverified-ID error path) for a low-complexity read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema coverage the baseline is 3, but the description adds value about valid parameter values – it explains that lst_… identifiers will not resolve to a profile and what error results. That is meaning the schema does not supply.

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?

States a specific verb and resource ('Full verified profile of one business') and enumerates the payload contents: services with price ranges, service area, opening hours, request policy. It does not name search_businesses as the sibling it complements, but the 'one business' scoping and the required ID make the distinction clear enough.

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?

Implicitly defines the workflow (obtain an ID via search_businesses, then fetch the full profile) and gives one explicit exclusion: IDs from the unverified list (lst_…) have no profile and return an unverified_listing error. There is no explicit 'use this instead of X when…' statement, so guidance is present but not complete.

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