franchisedata-mcp

Multi-Unit Franchisee Ownership Intelligence

get_operator_intelligence

Read-onlyIdempotent

Identify franchise owners and operators by store or operator ID. Retrieve entity trees, portfolio unit counts, and executive contacts to analyze multi-unit consolidation.

Instructions

PAID ($0.005). Retrieve corporate franchisee entity trees, operating LLCs, portfolio unit counts, and executive leadership contacts. Requires either 'operator_id' OR both 'brand' and 'store_id'. Atomically debits $0.005. Requires 'fc_live_...' API key. Returns 402 if balance insufficient. WHEN TO USE: Use to identify who owns and operates a franchise location (e.g. Flynn Group, Carrols), examine multi-unit consolidation, and find franchisee executive contacts. WHEN NOT TO USE: Do not use for corporate franchisor FDD financial benchmarks (use 'get_fdd_item19') or in-store hardware (use 'detect_tech_stack'). ALTERNATIVES: Use 'get_fdd_item19' for statutory Item 19 disclosures; use 'semantic_vector_search' to find operators by fuzzy concept.

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	No	Canonical brand slug (e.g. 'tacobell', 'applebees', 'wendys'). Used when querying by store.
`store_id`	No	Store ID (e.g. 'loc_tacobell_1001') to look up controlling franchisee.
`operator_id`	No	Direct operator entity ID (e.g. 'op_flynn_group'). Provide this OR provide both 'brand' and 'store_id'.

Output Schema

TableJSON Schema

Name	Required	Description
`operator`	No	Full operator profile when queried by operator_id
`operators`	No	List of operator associations when queried by brand/store
`balance_remaining_usd`	Yes	Remaining API credit balance in USD

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.1Oct 6, 2026

changedInput schema / properties / brand / description

Previous value: -"Brand slug (e.g. 'tacobell', 'mcdonalds', 'wendys')"New value: +"Canonical brand slug (e.g. 'tacobell', 'applebees', 'wendys'). Used when querying by store."

changedInput schema / properties / operator_id / description

Previous value: -"Optional direct operator ID"New value: +"Direct operator entity ID (e.g. 'op_flynn_group'). Provide this OR provide both 'brand' and 'store_id'."

changedInput schema / properties / store_id / description

Previous value: -"Store ID or store number"New value: +"Store ID (e.g. 'loc_tacobell_1001') to look up controlling franchisee."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "balance_remaining_usd": {
+      "description": "Remaining API credit balance in USD",
+      "type": "string"
+    },
+    "operator": {
+      "description": "Full operator profile when queried by operator_id",
+      "properties": {
+        "annual_revenue_usd": {
+          "type": "number"
+        },
+        "dba_name": {
+          "type": "string"
+        },
+        "headquarters": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "legal_name": {
+          "type": "string"
+        },
+        "total_units": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "operators": {
+      "description": "List of operator associations when queried by brand/store",
+      "items": {
+        "properties": {
+          "annual_revenue_usd": {
+            "type": "number"
+          },
+          "contact_role": {
+            "type": "string"
+          },
+          "dba_name": {
+            "type": "string"
+          },
+          "headquarters": {
+            "type": "string"
+          },
+          "legal_name": {
+            "type": "string"
+          },
+          "operator_id": {
+            "type": "string"
+          },
+          "total_units": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "balance_remaining_usd"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint/idempotentHint/openWorldHint), but the description adds substantial value: pricing ($0.005), the atomic debit, the required 'fc_live_...' API key, and the 402 insufficient-balance behavior. The only tension is the debit side effect against readOnlyHint, though this concerns billing rather than domain-data mutation, so it is supplemental rather than contradictory.

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?

Front-loads the cost and auth requirement, then sections usage guidance cleanly; nearly every sentence earns its place. Slight redundancy in naming get_fdd_item19 twice (WHEN NOT TO USE and ALTERNATIVES) keeps it just below top marks.

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

Completeness5/5

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

For a paid, key-gated read tool with an output schema, the description covers everything an agent needs: cost, auth, error behavior, selection rule, and routing to alternatives. Return-format details are correctly left to the output schema.

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 100% and the schema already documents brand, store_id, and operator_id as well as the OR relationship. The description restates the selection rule ('operator_id' OR both 'brand' and 'store_id'), which is helpful confirmation but adds little beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Retrieve corporate franchisee entity trees, operating LLCs, portfolio unit counts, and executive leadership contacts') and names concrete examples (Flynn Group, Carrols). It is immediately distinguishable from sibling lookups like get_fdd_item19 or detect_tech_stack.

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, WHEN NOT TO USE, and ALTERNATIVES sections name the exact sibling tools to route to (get_fdd_item19 for Item 19, semantic_vector_search for fuzzy operator search, detect_tech_stack for hardware). No condition is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server