Skip to main content
Glama

Search SOGC gazette publications

search_sogc_publications
Read-only

Search official Swiss Official Gazette of Commerce publications by keyword, rubric, and date range to find commercial-register mutations, bankruptcies, and debt enforcement notices.

Instructions

Search official Swiss Official Gazette of Commerce (SOGC/SHAB) publications: commercial-register mutations (HR), bankruptcies (KK), debt enforcement, and more. Filter by keyword, rubric and date range. Results are listed newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sogc_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
rubricNoRubric: HR=commercial register, KK=bankruptcy, LS=debt call, ES=inheritance, …HR
date_toNoLatest publication date YYYY-MM-DD
keywordNoFree-text keyword, e.g. a company name
date_fromNoEarliest publication date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new behavioral fact — results come back newest first — but says nothing about pagination beyond limit, truncation, or result cost.

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 compact sentences, front-loaded with the resource name and content types, and the ordering note is placed last where it belongs. The trailing "and more" is the only slightly wasteful phrase.

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?

For a read-only search tool with no output schema and 80% schema coverage, the description covers what the corpus contains, what can be filtered, and the sort order. Only the shape of returned entries and pagination behavior are unaddressed, which is a minor gap.

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 coverage is 80% and the rubric enum already spells out HR/KK/LS/ES meanings, so the schema does the heavy lifting. The description only restates that keyword, rubric, and dates are filters, adding no format or interaction detail (e.g. whether keyword matches company name only) beyond the schema.

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?

States a specific verb and resource — searching SOGC/SHAB publications — and enumerates the content types (commercial-register mutations HR, bankruptcies KK, debt enforcement) so an agent knows what corpus is behind it. It does not explicitly contrast itself with search_federal_gazette or search_companies, so the sibling differentiation is left implicit.

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?

"Filter by keyword, rubric and date range" implies how the tool is used, but there is no statement of when to choose it over search_federal_gazette or search_companies, and no exclusions or prerequisites. Usage is inferable but not spelled out.

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

Deploy Server

Other Tools