Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Read a company's legal notice

companies_legal_notice
Read-onlyIdempotent

The legal notice (Impressum) a company publishes on its own website, as German and Austrian law asks: its legal name and form, register court and number (with how companies_search finds it), the people who represent it, its VAT number, address, email and phone, each with the line of the notice it came from. Give its website, like the one a longlist shows; the notice is found from the home page or at the usual addresses. A site without one, or closed to bots by its robots.txt, costs nothing. Costs $0.01 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": {
      "website": "<website>"
    },
    "name": "companies_legal_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe company's website (dreherei-schaefer.de), or its notice's own address.

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?

Beyond the readOnly/openWorld/idempotent annotations it discloses the return payload field by field with per-field source lines, the discovery fallback, that a missing notice or robots.txt block is free, and the exact $0.01-per-call cost with no charge on failure. That is substantive behavioral context annotations do not carry.

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?

It front-loads what the notice contains, then follows with input, failure behavior and cost. Density is high but each clause (discovery fallback, robots.txt, pricing) carries information an agent needs.

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?

With no output schema, the description compensates by spelling out the returned fields and their provenance, and it covers input, failure modes and cost. Nothing needed to invoke it correctly is missing.

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 100% so the single 'website' param is already documented, but the description adds real meaning: an example domain (dreherei-schaefer.de), that it can be the website a longlist shows, or the notice's own address.

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

Purpose4/5

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

The description makes clear this reads a company's published legal notice (Impressum) and enumerates exactly what comes back: legal name and form, register court and number, representatives, VAT, address, email, phone. The read action is implicit via the title rather than a leading verb, and it never explicitly contrasts with siblings like companies_get, which carry overlapping attribute data.

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?

It tells the agent what to supply ('Give its website, like the one a longlist shows') and how the notice is located (from the home page or usual addresses). It stops short of naming alternatives or a when-not-to-use condition versus companies_get or companies_search.

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