Agent Company Index

Request company listing

request_listing

List one offering of the company you act for in the Agent Company Index. Listing is free. Before calling, fill answers from the company's website and ask the user for the rest: what problem the offering solves (primary_problem), who it fits best (positive_fit) and who not (negative_fit), two to four use_cases, the countries it serves (market_country), support_languages and pricing_model. Leave out anything you cannot confirm; unanswered fields stay visible on the profile as open questions. Returns a reference and a private listing token: tell the user to keep both, the token is shown only once. work_email must be an address on the company's own domain that the user reads (info@example.com); a free-mail or other-domain address is refused at once, because the approval is recorded for a mailbox on the domain (a company without one writes to ACI). Domain control: ACI mails that address an 8-digit code that the user gives back to you (verify_listing_domain email_code); where no code can be sent, a DNS TXT record or a file. Show the user the returned option word for word. ACI then drafts the profile from the website in a few minutes (get_listing_status). Once a person who may act for the company approves one exact revision and accepts the Listing Terms (approve_listing), it is published automatically. Payment never changes fit or order.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No
`answers`	No	Optional structured company answers for the draft. Each becomes a company statement on the profile, shown with its date. Unanswered fields stay open questions.
`website`	Yes	The company's own domain, e.g. example.com.
`work_email`	Yes	An address on the company's own domain (e.g. info@example.com) that the user can read: ACI mails it a code that confirms the domain without DNS changes. A free-mail address (Gmail, GMX, web.de, Outlook …) or an address on another domain is refused.
`schema_version`	Yes
`target_customers`	Yes	Who it is for and in which countries.
`product_or_service`	Yes	The one offering to list first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / work_email / description

Previous value: -"An address on the company's own domain (e.g. info@example.com) that the user can read: ACI mails it a code that confirms the domain without DNS changes. Another address works but then needs a DNS record or file."New value: +"An address on the company's own domain (e.g. info@example.com) that the user can read: ACI mails it a code that confirms the domain without DNS changes. A free-mail address (Gmail, GMX, web.de, Outlook …) or an address on another domain is refused."

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / work_email / description

Previous value: -"Where ACI replies."New value: +"An address on the company's own domain (e.g. info@example.com) that the user can read: ACI mails it a code that confirms the domain without DNS changes. Another address works but then needs a DNS record or file."

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / answers

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional structured company answers for the draft. Each becomes a company statement on the profile, shown with its date. Unanswered fields stay open questions.",
+  "properties": {
+    "certifications": {
+      "description": "Certifications held by the company itself, not by its hosting provider.",
+      "items": {
+        "maxLength": 200,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "company_name": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "company_size_bands": {
+      "description": "Size of the company itself.",
+      "items": {
+        "enum": [
+          "micro",
+          "small",
+          "medium",
+          "large",
+          "enterprise"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "data_export": {
+      "description": "How customers get their data out.",
+      "maxLength": 500,
+      "type": "string"
+    },
+    "data_residency": {
+      "description": "Where customer data is stored.",
+      "enum": [
+        "DE",
+        "EU",
+        "US",
+        "mixed"
+      ],
+      "type": "string"
+    },
+    "deployment_model": {
+      "enum": [
+        "cloud",
+        "on_premises",
+        "both",
+        "not_applicable"
+      ],
+      "type": "string"
+    },
+    "description": {
+      "maxLength": 500,
+      "minLength": 20,
+      "type": "string"
+    },
+    "headquarters_country": {
+      "pattern": "^[A-Z]{2}$",
+      "type": "string"
+    },
+    "limitations": {
+      "items": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "market_country": {
+      "pattern": "^[A-Z]{2}$",
+      "type": "string"
+    },
+    "minimum_contract_term": {
+      "maxLength": 500,
+      "type": "string"
+    },
+    "negative_fit": {
+      "items": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "offering_name": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "offering_status": {
+      "enum": [
+        "active",
+        "beta",
+        "discontinued",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "offering_type": {
+      "enum": [
+        "software",
+        "service",
+        "physical_product",
+        "platform",
+        "other"
+      ],
+      "type": "string"
+    },
+    "organization_status": {
+      "enum": [
+        "active",
+        "inactive",
+        "acquired",
+        "closed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "positive_fit": {
+      "items": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "prerequisites": {
+      "description": "What a customer needs in place before using the offering.",
+      "items": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pricing_model": {
+      "maxLength": 300,
+      "type": "string"
+    },
+    "pricing_visibility": {
+      "enum": [
+        "public",
+        "quote_required",
+        "undisclosed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "primary_problem": {
+      "maxLength": 300,
+      "type": "string"
+    },
+    "sub_processors": {
+      "items": {
+        "maxLength": 200,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "support_languages": {
+      "items": {
+        "pattern": "^[a-z]{2,3}(-[A-Z]{2})?$",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "target_customers": {
+      "items": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "target_size_bands": {
+      "description": "Size of the customer organizations the offering is for.",
+      "items": {
+        "enum": [
+          "micro",
+          "small",
+          "medium",
+          "large",
+          "enterprise"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "use_cases": {
+      "items": {
+        "maxLength": 300,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "website_url": {
+      "description": "Company-confirmed primary website URL: https, on the company domain or a subdomain. Use when the root moves visitors elsewhere client-side.",
+      "maxLength": 2048,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false, openWorld=true) by disclosing non-obvious outcomes: the listing token is shown only once and must be kept, unanswered fields stay visible as open questions, approval triggers automatic publication, and payment never affects fit or order. The domain-control options (code, DNS TXT, file) are also disclosed.

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-loaded with the purpose and the free-listing fact, and virtually every sentence carries operational value (email rule, token warning, approval flow). It is a dense run-on paragraph, though, and would scan better broken into short grouped lines.

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?

No output schema exists, yet the description explains the return payload (reference plus private listing token) and the downstream lifecycle, which is what an agent needs. Against a 7-parameter tool with a 25+ property nested answers object, it guides the high-value fields but is not a full field-by-field reference.

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 coverage is 71%, so the schema carries much of the load, but the description adds real meaning: which fields to derive from the website vs ask the user (primary_problem, positive_fit, negative_fit, use_cases, market_country, support_languages, pricing_model) and the 'leave out anything you cannot confirm' rule. It does not cover the remaining ~29% of undocumented nested fields such as limitations, prerequisites, or certifications.

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 ('List one offering of the company you act for in the Agent Company Index'), plus the scope constraint (one offering, the company's own). It is immediately distinguishable from siblings like request_listing_removal, update_listing_answers, and approve_listing without opening any schema.

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?

Explicitly sequences the workflow: fill what you can from the website, ask the user for the rest, then hand off to verify_listing_domain, get_listing_status, and approve_listing. It also states a hard pre-condition (work_email must be on the company's own domain, free-mail refused) and a fallback (a company without one writes to ACI).

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

All Agent Company Index tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?