Skip to main content
Glama

Brreg No

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Sub Entities

search_sub_entities
Read-onlyIdempotent

Search sub-entities/branches (underenheter) — e.g. local establishments of a parent company. Results under _embedded.underenheter. Filter by overordnetEnhet (parent org number) and/or navn. e.g. {overordnetEnhet:"923609016"} lists Equinor branches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
navnNoFull-text name search.
pageNoZero-based page number (default 0).
sizeNoResults per page (default 20).
kommunenummerNoMunicipality number, e.g. "0301".
overordnetEnhetNoParent entity org number, e.g. "923609016".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "overordnetEnhet": "923609016"
+  },
+  {
+    "kommunenummer": "0301",
+    "navn": "avd"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds useful behavioral context by specifying where results are located (_embedded.underenheter) and providing a concrete example. No contradiction with annotations.

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

Conciseness5/5

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

The description is concise and front-loaded with purpose, followed by key usage details and an example. Every sentence earns its place with no redundant information.

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 compensates by disclosing the result location (_embedded.underenheter) and giving an illustrative example. It covers the essential behavioral aspects for correct invocation, though it could explicitly mention pagination parameters.

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 description coverage is 100%, so the baseline is 3. The description reinforces the meaning of overordnetEnhet and navn but does not add substantial new semantic meaning beyond what the schema already provides.

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 clearly states the tool searches sub-entities/branches (underenheter), with a specific verb and resource. It distinguishes from sibling tools like search_entities by specifying the sub-entity scope and giving a concrete example.

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?

The description provides clear context on when to use the tool, such as finding local establishments of a parent company and filtering by parent org number or name. It does not explicitly exclude alternatives like search_entities, but the example and scope make intended usage clear.

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

All Brreg No 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