Skip to main content
Glama

agentready.ch: Swiss company directory

Search Swiss companies

search_companies
Read-onlyIdempotent

Searches the public profiles of Swiss firms on agentready.ch by trade, service, place, firm name or website, e.g. «Fahrschule Winterthur» or «loaded.ch». Returns up to limit firms, each with slug, name, category, region, short description, services, the full profile link (profile_url_absolute) and can_contact (whether the firm takes messages through agentready.ch). A query with a website returns the profile on that domain first, with exact_match: true; when no result has exact_match: true, that firm is not listed.

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": {
      "query": "<query>"
    },
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat the user looks for: trade, service, firm name, place or website, e.g. «Fahrschule Winterthur» or «loaded.ch».
regionNoOptional. A town, canton or region, e.g. Winterthur or Zug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +20
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / query / description
      Previous value: -"Name, category, region, service or website (e.g. loaded.ch)."New value: +"What the user looks for: trade, service, firm name, place or website, e.g. «Fahrschule Winterthur» or «loaded.ch»."
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Optional. A town, canton or region, e.g. Winterthur or Zug.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"Name, category, region, service or website (e.g. loaded.ch)."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false), so the description is free to spend its words elsewhere — and it does, disclosing the result cap ('up to limit firms'), the returned field set, the meaning of can_contact, and the exact_match semantics for domain queries. The negative inference ('when no result has exact_match: true, that firm is not listed') is genuinely useful behavioral context an agent could not derive from annotations or schema.

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?

Three sentences, front-loaded with purpose and return shape, then the exact_match rule last where it belongs. The only waste is the repeated example pair («Fahrschule Winterthur» / «loaded.ch»), which already appears verbatim in the query parameter description.

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-value burden and does so by listing slug, name, category, region, short description, services, profile_url_absolute and can_contact. Combined with the exact_match rule and the limit cap, an agent has enough to call it and interpret results; only pagination beyond limit (max 20) and the general empty-result case go unstated.

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 67%, with query and region documented but limit carrying only default/maximum/minimum. The description compensates: it widens query semantics beyond the schema's example by naming the five accepted facets, ties limit to result cardinality ('returns up to limit firms'), and explains that a website-valued query changes ranking via exact_match. region is the only parameter left without added narrative meaning.

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 opens with a specific verb and resource — searching public profiles of Swiss firms on agentready.ch — and enumerates the queryable facets (trade, service, place, firm name, website). It never names the natural companion tool read_company_profile, so the boundary between a search hit and a full profile read is left for the agent to infer from the returned profile_url_absolute.

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

Usage Guidelines3/5

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

Usage is implied through worked examples («Fahrschule Winterthur», «loaded.ch») and through the website-query behavior, which tells the agent a domain lookup is a legitimate call pattern. There is no explicit when-to-use/when-not statement and no routing to sibling tools such as read_company_profile or send_contact_request, so an agent must infer the search-then-read workflow.

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.

Resources