Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Look up a company

lookup_company
Read-onlyIdempotent

What a company is, from its domain: name, description, location, industries, size, funding, languages, the technologies its site uses, its shared mailboxes (info@, sales@ ...) and phone numbers, and its social profiles. From Conecto's index of public company facts, else from its own homepage. Never people. The business's Conecto inboxes never write first to a mailbox found here. $0.05 when found; free when nothing is known. Costs $0.05 per call; nothing if it fails.

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": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe company's web address, e.g. hansenvoss.example.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only carry the safe-read profile; the description goes well beyond them with the data provenance chain, the per-call price ($0.05 when found, free when nothing is known, nothing if it fails), and the policy that Conecto inboxes never initiate outreach to a mailbox discovered here. These are non-obvious operational facts an agent cannot get from the schema or annotations.

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 returned-fields list is front-loaded and the exclusions follow, which is the right order. The pricing is stated twice – "$0.05 when found; free when nothing is known" and then "Costs $0.05 per call; nothing if it fails" – which is one sentence more than needed.

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?

With no output schema, the description carries the return contract and does so by enumerating every field group the agent should expect. What is missing is narrower: how partial or ambiguous results look, and whether a failed domain lookup is distinguishable from an unknown company.

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?

There is a single required parameter, at 100% schema coverage, and the schema already defines it as a web address with a worked example. The description's "from its domain" adds nothing about accepted formats or normalization, so 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?

The description names the resource (a company) and the input that identifies it (its domain), then enumerates exactly what comes back: name, description, location, industries, size, funding, languages, site technologies, shared mailboxes, phone numbers, social profiles. That level of specificity makes the tool unmistakable next to companies_get or companies_search.

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

Usage Guidelines4/5

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

"Never people" is an explicit exclusion, and the source-order fallback (Conecto index first, then the company's own homepage) tells the agent what it is actually querying. No sibling tool is named by way of contrast, so the agent has to infer that this is the domain-first enrichment path rather than a company record fetch.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources