Skip to main content
Glama

Local business address metadata

bpj_local_business_address_metadata
Read-onlyIdempotent

Build LocalBusiness metadata with a PostalAddress, locality, postal code and two-letter country code.

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": {
      "name": "<name>",
      "street": "<street>",
      "city": "<city>",
      "code": "<code>",
      "country": "<country>"
    },
    "name": "bpj_local_business_address_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
codeYes
nameYes
streetYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that the output is a LocalBusiness metadata structure with a PostalAddress; it does not say whether the result is a JSON object, JSON-LD snippet, or markup, nor how invalid or non-two-letter country codes are handled.

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?

A single well-formed sentence with no filler, front-loading the verb and output resource. It is arguably too terse rather than padded, which is the right failure mode.

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 simple five-required-parameter pure builder with no output schema, the definition covers purpose but omits return shape and validation behavior, which an agent needs to chain the result into further calls. Adequate but with clear gaps given no output schema exists to explain the return value.

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

Parameters2/5

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

Schema description coverage is 0% (titles and maxLength only), so the description carries the burden but only partially compensates. It effectively maps city→locality, code→postal code, country→two-letter code, and street/name→PostalAddress, but never explains the role of `name` or the expected format of `street`, leaving one of five required parameters uninterpreted.

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?

Uses a specific verb (Build) with a specific resource (LocalBusiness metadata) and names the constituent structure (PostalAddress, locality, postal code, country code). It is clearly distinct from arithmetic/date siblings like bpj_business_day_offset, though it does not explicitly contrast with adjacent metadata builders such as bpj_service_area_metadata.

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?

The description implies usage (constructing schema.org-style LocalBusiness metadata from address parts) but gives no explicit when-to-use, when-not-to-use, or alternative guidance. With many sibling *_metadata builders, an agent gets only an indirect signal that this one is for business addresses.

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.