Skip to main content
Glama

Get business profile

get_business_profile
Read-onlyIdempotent

Get a business profile's details as last synced from Google: name, address, phone, website, description, categories, hours, special hours, services, attributes, service area and completeness score.

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

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world profile, so credit goes to the added context: 'as last synced from Google' discloses that results are a cached snapshot rather than live data, which is behaviorally meaningful and not in the annotations.

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 whose only elaboration is the field enumeration that doubles as return-value documentation since no output schema exists. Every element earns its place.

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?

With no output schema, the field list is essential and present, so an agent knows what it gets back. What's missing is how to supply profile_id and what happens if the profile has never been synced.

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 description coverage is 0%, and the description never mentions profile_id at all — no guidance on where to obtain the UUID (presumably list_business_profiles). The parameter name is self-explanatory, so this is a gap rather than a failure, but the description does not compensate for the empty schema.

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+resource ('Get a business profile's details') and enumerates the returned fields, which makes the scope unambiguous. It never explicitly contrasts with list_business_profiles or sync_profile, so sibling differentiation is left to the reader.

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: it retrieves a single profile by id and the phrase 'as last synced from Google' hints that data is a snapshot, but there is no explicit statement about when to call this versus list_business_profiles or sync_profile to refresh.

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