Skip to main content
Glama

Fix an entity map

fix_entitymap
Read-onlyIdempotent

Use when a site has no entitymap.json, or to replace a wrong one. Returns a starter entitymap.json built from the domain's latest scan record: business name, phone, coordinates and declared service areas as entities with SERVES relations. Fields the site never stated are marked TODO, never guessed. Read-only; needs a prior scan of the domain (run scan_domain first if there is none).

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": {
      "domain": "<domain>"
    },
    "name": "fix_entitymap"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it explains the output is built from the latest scan record, fields are 'marked TODO, never guessed,' and a prior scan is required. It does not cover error behavior if the scan record is missing, but the disclosed behavior is strong.

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?

The description is front-loaded with usage, then explains output and prerequisites in a logical sequence. It is appropriately sized for the tool's complexity, though the phrase 'Read-only' repeats what the readOnlyHint annotation already states, which is a minor redundancy.

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?

Given there is no output schema, the description helpfully explains what the return value contains (starter entitymap.json with entities and SERVES relations, TODO markers for unstated fields). The prerequisite scan requirement is also stated. The missing domain format detail is a small completeness gap.

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%, so the description must compensate for the single parameter. It implies the domain parameter refers to the domain whose latest scan record is used, but it does not specify the expected format (e.g., bare domain vs. URL). This is minimum viable parameter meaning.

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

Purpose5/5

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

The description uses a specific verb and resource: 'Returns a starter entitymap.json built from the domain's latest scan record.' It clearly distinguishes itself from the sibling scan_domain by naming it as a prerequisite, so an agent can tell when to call this tool instead of running a scan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance is given: 'Use when a site has no entitymap.json, or to replace a wrong one.' It also names the alternative prerequisite action: 'needs a prior scan of the domain (run scan_domain first if there is none).' This leaves little ambiguity about conditions for invocation.

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.