Skip to main content
Glama

Service area metadata

bpj_service_area_metadata
Read-onlyIdempotent

Build Service metadata with a provider and an explicit list of served administrative areas.

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": {
      "service": "<service>",
      "provider": "<provider>",
      "areas": "<areas>"
    },
    "name": "bpj_service_area_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
areasYes
serviceYes
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/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 elsewhere. The description adds almost nothing behavioral: it doesn't say the result is a returned structure rather than a persisted record, doesn't explain how the areas string is parsed, and doesn't describe the shape of what comes back. Given the annotations carry the burden, this still leaves a notable gap.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the cause of the semantic gaps noted above.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter builder with no output schema and no param descriptions, the definition should explain the areas input encoding and what the constructed result contains. Neither is covered, so an agent would have to guess at the call contract.

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%, so the description is the only source of parameter meaning. It names 'provider' and 'areas' and clarifies that areas is an explicit served-administrative-area list, but it says nothing about the required newline-delimited format (only hinted at in the schema title), the value space for 'service', or any of the maxLength constraints. Two of three parameters get only a restatement of their field names.

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 names a verb ("Build") and a resource ("Service metadata") plus the two main input dimensions, so the basic intent is graspable. However, "metadata" is the same generic framing used by the many sibling *_metadata builders, and nothing here distinguishes this tool's output or use case from those. An agent knows roughly what it constructs but not why or when this one is the right builder.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool or condition. The agent must infer applicability entirely from the name and inputs.

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.