Stonewake

Company sector context

company_sector_context

Read-onlyIdempotent

Official German statistics beside one German company: the corporate insolvency and enterprise figures Destatis publishes for its WZ 2008 section and its Bundesland, each with its table code, period, retrieval time, source link and the licence attribution line, which must be shown with the figure. Takes node_id, the graph node id from search_companies hits. No German register states a company's NACE code, so pass nace (a section letter or a NACE code such as 41.20) to name the sector; the answer then says the caller named it. missing lists in plain sentences what is not held, and the Kreis the regional context places it in. Aggregates for context only, never part of the company's score or status.

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": {
      "node_id": "<node_id>"
    },
    "name": "company_sector_context"
  }
}

Input Schema

Name	Required	Description
`nace`	No	A NACE or WZ 2008 code naming the sector, for example F, 41 or 41.20.
`locale`	No	The language of indicator_label, breakdown_label and unit, en by default; the table's own German rides beside each in *_source.
`node_id`	Yes	The graph node id, as returned by search_companies hits. Not the entity_id of company_profile.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / locale

Added value: +{
+  "description": "The language of indicator_label, breakdown_label and unit, en by default; the table's own German rides beside each in *_source.",
+  "enum": [
+    "en",
+    "de"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 25, 2026
- addedInput schema / properties / nace / pattern
```
Added value: +"^[A-Za-z]?\\s?(\\d{2}(\\.\\d{1,2}){0,2})?$"
```
Changed1 schema field changedOct 12, 2026
- addedInput schema / properties / node_id / maximum
```
Added value: +2147483647
```
AddedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, yet the description adds real behavioral context: the licence attribution line must be displayed with the figure, provenance is disclosed ('the answer then says the caller named it'), and missing data is reported in plain sentences. It does not address error behavior or response size, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and largely front-loaded, but sentences are long and clause-heavy (the licence obligation is embedded mid-sentence and effectively restated), making them slower to parse than necessary. Little is wasted, but structure could be tighter.

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-shape burden and does so well — listing every field, the `missing` behavior, and the Kreis. Only failure modes (bad node_id, no data at all) are unaddressed, a minor gap for a read-only lookup.

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 baseline is 3, but the description earns more: it disambiguates node_id ('as returned by search_companies hits. Not the entity_id of company_profile') and explains the reason for nace plus its observable side effect on the answer. The locale parameter is left entirely to 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?

The description names a specific resource (Destatis insolvency and enterprise figures for a company's WZ 2008 section and Bundesland) and enumerates the accompanying fields (table code, period, retrieval time, source link, licence line). It is clearly not the same as company_regional_context or company_financials, though it does not explicitly name a sibling to distinguish itself from.

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 states the entry path ('the graph node id from search_companies hits'), explains precisely when and why to supply nace (no German register carries NACE codes), and sets a hard usage boundary: 'Aggregates for context only, never part of the company's score or status.' What is missing is explicit routing against the closest sibling, company_regional_context, which also covers regional context.

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

All Stonewake tools Inspect

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

Need Help?