Skip to main content
Glama

Honeyfield Marketing MCP

Business Profile: Location info

gbp_location_info
Read-only

Stammdaten des Business-Profil-Standorts: Name, Adresse, Telefon, Kategorie, Öffnungszeiten. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gbp_location_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds little beyond the field list. It never explains how the target location is identified when the only parameter is a workspace slug, nor whether all locations are returned or a single one — a real ambiguity for an external-API read.

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 short lines, front-loaded with what data the tool concerns before the parameter note. No filler; the field enumeration is dense but purposeful.

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?

An output schema exists, so return values need not be explained, and the read-only nature is annotated. What is missing is how a specific location is targeted and how this differs from overlapping GBP siblings, which matters given the large sibling set.

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?

Schema description coverage is 0%, so the description must carry the single parameter, and it does: it names 'workspace' as the customer workspace slug and notes it is optional when only one workspace exists. That is meaningfully more than the bare anyOf string schema provides, though it omits format/error behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (Business-Profil-Standort master data) and enumerates the fields involved (name, address, phone, category, hours), which orients the agent. But there is no explicit verb and no differentiation from the very similar siblings gbp_get_profile, gbp_list_locations, gbp_manage_hours and gbp_manage_open_info, so an agent cannot confidently tell whether this reads or writes those fields.

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?

No statement of when to use this tool versus gbp_get_profile or gbp_list_locations, and no preconditions (permissions, whether a location must already be selected). The only conditional text concerns the workspace parameter, not tool selection.

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